On Apr 29, 12:30 am, Michael Bayer wrote:
> The next issue is, this was a known issue that is fixed in both 0.6.7 and 0.7
> (ticket 2100, unfortunately I had to go through creating a whole test just
> now to figure that out, but there you go). And, if you name your column
> "group" or "
I have a problem with oracle column names that are oracle reserved
words (http://download.oracle.com/docs/cd/B19306_01/em.102/b40103/
app_oracle_reserved_words.htm). I read through the archive and found:
https://groups.google.com/group/sqlalchemy/browse_thread/thread/5e2699594c73fe1c/41f35436c91498
Hi Michael,
On Apr 20, 11:20 am, Michael Bayer wrote:
> yeah that is pretty awful, Oracle is super picky about names, and there's
> already a lot of stuff to appease its limitations with bind parameters. The
> bind name is ultimately derived from the "key" of the column so this would
> chan
Hi Michael,
On Apr 20, 11:20 am, Michael Bayer wrote:
> yeah that is pretty awful, Oracle is super picky about names, and there's
> already a lot of stuff to appease its limitations with bind parameters. The
> bind name is ultimately derived from the "key" of the column so this would
> chan
Hi,
I have a little problem with column names that start with a digit at
an oracle databases which I inherited.
When I try to do and update/insert with values from a dict like this
i.e.:
---8<--
engine =create_engine('oracle+cx_oracle://')
engine.echo = True
Session = sessionmaker(bind=engine)
se
