On Tue, Mar 20, 2018 at 08:32:14PM -0400, Mike Bayer wrote:
> I think it would be a lot easier to have the corresponding translation
> linked off using relationship(). can you work with that?
I could .. :) I'll make some "helper functions" or maybe a custom Query
object, with maybe some
I'm moving data from one table to another. During this move I'm preserving
the ID of the old table before dropping it. However, by doing so the
sequence gets out of whack and the database will no longer allow inserts to
the trigger table. What can I do to fix the broken sequence? The id
On Fri, Mar 23, 2018 at 6:58 PM, Colton Allen wrote:
> I'm trying to reset my primary key sequence and its raising a weird error.
> My primary key is a UUID.
>
> op.execute(
> sa.select([
> sa.func.setval(
> 'trigger_id_seq',
>
I'm starting to write an application which will have two versions. One is
single-user with sqlite3 as the backend, the other is multi-user with
postgres as the backend. The single-user version will be written first.
Both will be placed on github as F/OSS applications.
Please point me to
Thank you, excellent explanation! Setting autoflush off fixed the issue.
In the end I created the Filter objects directly and set directory and
category on them, which generated a single INSERT. It was generating a ton
of SELECT / INSERT the way I was initially doing it.
On Saturday, March