- attached oracle.utf8.patch
Oracle dialect generates too long index names
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.
Comments (7)
-
Account Deleted -
repo owner - changed milestone to 0.4.xx
im assuming the autosetinputsizes change is not part of the change...
-
Account Deleted - attached oracle.patch
Patch agaist SA 4.0 release
-
Account Deleted 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).
-
Account Deleted (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).
-
repo owner - changed status to resolved
-
repo owner - removed milestone
Removing milestone: 0.4.xx (automated comment)
- Log in to comment
This is a possible (general) patch for too long identifier.