- changed title to SQLAlchemy/Oracle generates alias indentifiers too long for tables when the column name is exactly 30 characters ?
SQLAlchemy/Oracle generates alias indentifiers too long for tables when the column name is exactly 30 characters ?
DatabaseError: (DatabaseError) ORA-00972: identifier is too long
The generated sql contains an alias identifier 32 characters long, the maximum allowed by oracle is 30.
Here is a sample of generated sql: 'SELECT curation.tmx_relationship_tag.id AS curation_tmx_relationshi_1, curation.tmx_relationship_tag.identifier AS curation_tmx_relationshi_2, ... tmx_entity_tag_1.last_update_work_unit_id AS tmx_entity_tag_1_last_up_13 FROM curation.tmx_relationship_tag LEFT OUTER JOIN curation.tmx_relationship_tag_children tmx_relationship_tag_children_1 ON curation.tmx_relationship_tag.id = tmx_relationship_tag_children_1.relationship_tag_id LEFT OUTER JOIN curation.tmx_entity_tag tmx_entity_tag_1 ON tmx_entity_tag_1.id = tmx_relationship_tag_children_1.entity_tag_id WHERE :param_1 = curation.tmx_relationship_tag.document_id
Comments (7)
-
repo owner -
repo owner I'm behind a firewall and can't commit, but ignore my previous comment. the attached patch should be committed to resolve this issue.
-
repo owner - changed status to resolved
-
Account Deleted - changed status to open
- removed status
I still get the same problem when using eager loading using SQLAlchemy 0.5.4p2.
-
Account Deleted - attached thirty_char.py
Eager loading and 30 characters limit issue demonstration
-
repo owner backported 0.6 fix in b4887245b831d9795d711c084315e71ca0bb74c0 in e58b66838d95e9c5e57f3567940f619c730a7d69.
-
repo owner - removed milestone
Removing milestone: 0.5.6 (automated comment)
- Log in to comment
please post a test case for this issue as well as the version of SQLA in use (only 0.4.8 or 0.5.2 will be considered).