Re: [sqlalchemy] Proper way to handle new 128 character identifier limit in Oracle >= 12.2

2019-05-08 Thread Chris Stephens
I think you would actually want to query v$parameter since "compatible" can be set to a lower version than server which disables 128 lengths. SQL> select value from v$parameter where name = 'compatible'; VALUE -- 12.2.0 On Thursday, November 8, 2018 at 10:30:19 AM UTC-6, Mike Bayer

Re: [sqlalchemy] Proper way to handle new 128 character identifier limit in Oracle >= 12.2

2018-11-08 Thread Mike Bayer
On Thu, Nov 8, 2018 at 11:23 AM 'Van Klaveren, Brian N.' via sqlalchemy wrote: > > Hi, > > Oracle 12.2 now allows 128 character length identifiers: > > https://docs.oracle.com/en/database/oracle/oracle-database/12.2/newft/new-features.html#GUID-64283AD6-0939-47B0-856E-5E9255D7246B > > It'd be

[sqlalchemy] Proper way to handle new 128 character identifier limit in Oracle >= 12.2

2018-11-08 Thread 'Van Klaveren, Brian N.' via sqlalchemy
Hi, Oracle 12.2 now allows 128 character length identifiers: https://docs.oracle.com/en/database/oracle/oracle-database/12.2/newft/new-features.html#GUID-64283AD6-0939-47B0-856E-5E9255D7246B It'd be great if sqlalchemy knew about this, but what's the proper way of handling this? Just use the