On Monday, June 2, 2014 6:18:42 PM UTC-4, Michael Bayer wrote:
there’s nothing on the Python library side that could do that, someone had
> to have run an ALTER SEQUENCE on the database side in order for that to
> happen.
I don't even think you could use ALTER SEQUENCE in this situation. I
Bayer
Sent: Wednesday, June 25, 2014 4:27 PM
To: sqlalchemy@googlegroups.com
Subject: Re: [sqlalchemy] Oracle with sequence for primary key and that
sequence out of sync
On 6/25/14, 5:50 AM, Ofir Herzas wrote:
Sorry to barge in, but I'm having the exact same issue and I'm pretty sure
On 6/25/14, 5:50 AM, Ofir Herzas wrote:
> Sorry to barge in, but I'm having the exact same issue and I'm pretty
> sure no one altered the sequence manually.
> I'm using sqlalchemy 0.8, python 2.7.6, rhel 6.5, oracle 10g,
> cx_oracle with the same connection string as above
>
> This issue started j
Sorry to barge in, but I'm having the exact same issue and I'm pretty sure
no one altered the sequence manually.
I'm using sqlalchemy 0.8, python 2.7.6, rhel 6.5, oracle 10g, cx_oracle
with the same connection string as above
This issue started just recently after running ok for more than a thou
On Jun 2, 2014, at 1:17 PM, Scott Koranda wrote:
>
> I investigated and found that the sequence seq_admin_groups_id
> was now at the value 68 after having been used previously to
> insert rows with IDs in the 500s.
>
> I stopped the code and used sqlplus to change the sequence
> back to a valu
Hello,
I am using SQLAlchemy 0.9.4 with Python 2.6.6 on RHEL 6.5 with
Oracle 11.2.0.3.
My simple application queries an LDAP directory to find
particular records and then reflects the information into an
Oracle table. The application is designed to keep the database
table version of the informati
