Closed
Description
Migrated issue, originally created by Anonymous
This issue exists in 3.11
in _execute
raise exceptions.SQLError(context.statement, context.parameters, e)
sqlalchemy.exceptions.SQLError: (DatabaseError) ORA-00972: identifier is too long
'CREATE INDEX ix_r_5_0_was_r_notify_user_name ON r_5_0_was_r_notify (user_name)' {}
This patch works around the issue by truncating the index to the max_identifier_length() specified by the dialect.
Attachments: oracle.patch | oracle.utf8.patch
Metadata
Metadata
Assignees
Labels
Type
Projects
Relationships
Development
No branches or pull requests
Participants
Activity
sqlalchemy-bot commentedon Oct 18, 2007
Anonymous wrote:
This is a possible (general) patch for too long identifier.
sqlalchemy-bot commentedon Oct 18, 2007
Changes by Anonymous:
sqlalchemy-bot commentedon Oct 19, 2007
Michael Bayer (@zzzeek) wrote:
im assuming the autosetinputsizes change is not part of the change...
sqlalchemy-bot commentedon Oct 19, 2007
Changes by Michael Bayer (@zzzeek):
sqlalchemy-bot commentedon Oct 23, 2007
Anonymous wrote:
Patch agaist SA 4.0 release
sqlalchemy-bot commentedon Oct 23, 2007
Changes by Anonymous:
sqlalchemy-bot commentedon Oct 23, 2007
Anonymous wrote:
Added patch against SA 0.4 (pardon the dyslexia)
autosetinputsizes is not really part of the change, however I seem to require it with Oracle 10g with UTF8 (testing on Win32 if that makes a difference).
sqlalchemy-bot commentedon Jun 13, 2008
Anonymous wrote:
(original author: ged) Doesn't this problem also exists for other DBMS? (I think I've had it with Postgres) and there is also a similar problem with table names (see ticket 571).
sqlalchemy-bot commentedon Jun 22, 2008
Michael Bayer (@zzzeek) wrote:
bd708ad 8c1f08c
sqlalchemy-bot commentedon Jun 22, 2008
Changes by Michael Bayer (@zzzeek):