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 "fondly" remember Oracle sequences needing to be dropped and re-added with a lot of NEXTVALs... or using chunks of PL/SQL scripts to otherwise modify the sequence. Doing a quick look online, it seems like things still work the same way. If I were in this situation, I would enable a lot of query and connection logging, and then comb through the logs to see what was happening. For a variety of reasons, this doesn't seem like it should be possible. Is it possible that some records were being inserted with a numeric id that was originally generated by .nextval() in your app, but has since been incremented only in Python ? -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
