Open mrkafk opened 9 years ago
Having the same problem with many-to-many association table, the INSERT
operation is attempted twice.
I'm running in to this issue too. Does anyone have a fix?
I have the same problem here.
Many to many relationship, Pyramid, without polymorphic.
Also having same problem.
Hey Guys,
This just happen to me to. I discover that at least in my case the issue was that I called twice the function make_versioned. So in my scenario I had:
And it works properly if I do not call make_versioned twice. :)
I tried call make_versioned only once but no difference. Any updates for this issue?
I'm using:
Backend is PG 9.3. It seems like many-to-many handling still does not work correctly with Continuum for following definitions:
In a test I'm adding a License to some OSSVersions:
This fails as follows:
The basic reason is obvious: history table "assoc_ver_shallow_lic_version" has primary key constraint "assoc_ver_shallow_lic_version_pkey" which is required to be unique, while Continuum adds several records to it using the same transaction_id:
I'm using this with Pyramid which has generated a script for initializing the db, although it consists mostly of "Base.metadata.create_all(engine)", this results in following DDL for the association table:
The worrisome aspect I've noticed is that when I run "is_versioned(assoc_ver_shallow_lic_table)" I get False.
Is there some special way that many-to-many association tables should be configured for Continuum or is this a bug?