There are - to one relationships. E.g. X1 (deleted), X2 (inserted), Y1 (updated
FK from X1 to X2).
Andrus
On Feb 18, 2011, at 12:25 AM, Aristedes Maniatis wrote:
> On 18/02/11 12:53 AM, Andrus Adamchik wrote:
>> Then there are cases that don't have correct ordering at all. Usually this
>> invo
On 18/02/11 12:53 AM, Andrus Adamchik wrote:
Then there are cases that don't have correct ordering at all. Usually this
involves cyclic relationships. I don't have an example handy, but IIRC we
discussed that some time ago.
Would it make sense to perform all deletes before all inserts? Or are
Agreed. We've started following that practice too. Always assign a simple
unrelated primary key. Consistent, avoids surprises.
On Thu, Feb 17, 2011 at 9:09 AM, Mike Kienenberger wrote:
> Solution C: assign a meaningless primary key to the join table.
>
> Obviously, this isn't an option for ev
Solution C: assign a meaningless primary key to the join table.
Obviously, this isn't an option for everyone.
On Thu, Feb 17, 2011 at 3:11 AM, Aristedes Maniatis wrote:
> On 15/02/11 2:04 PM, Marcin Skladaniec wrote:
>>
>> java.sql.SQLIntegrityConstraintViolationException: The statement was
>> a
Then there are cases that don't have correct ordering at all. Usually this
involves cyclic relationships. I don't have an example handy, but IIRC we
discussed that some time ago.
Andrus
On Feb 17, 2011, at 3:29 PM, Bryan Lewis wrote:
> This sounds like the same problem we've lived with for ye
This sounds like the same problem we've lived with for years. In a
complicated model (hundreds of entities for us), Cayenne's graph-following
algorithm (AshwoodEntitySorter) doesn't have enough information to perform
all the commits in exactly the right order. (Perhaps this is an argument
for sup
17.02.2011 09:11
Bitte antworten an
user@cayenne.apache.org
An
user@cayenne.apache.org
Kopie
Thema
Re: possible bug with inherited cayenne objects and mandatory fields
On 15/02/11 2:04 PM, Marcin Skladaniec wrote:
> java.sql.SQLIntegrityConstraintViolationException: The statement
On 15/02/11 2:04 PM, Marcin Skladaniec wrote:
java.sql.SQLIntegrityConstraintViolationException: The statement was aborted
because it would have caused a duplicate key value in a unique or primary key
constraint or unique index identified by 'TAGRELATION_UNIQUE' defined on
'TAGRELATION'.
Ca
Hi Michael
Yes, the qualifier is filled in. This cayenne model was in use for a
long time, we only added some NOT NULL and UNIQUE constraints recently,
and now the error showed up.
This is what I do (in java) and relevant sql logs (simplified):
DataContext cc =
AngelServer.getDa
Hi Marcin,
Most likely your unique index is causing some grief. Any chance you
are logging the SQL and can post it?
Also, is "entityIdentifier" being used for inheritance in Cayenne?
(Did you fill something in the "Qualifier" field in the ObjEntity?)
If so, it sounds like you are using it as a s
Hello
I have run into a problem which seems to be a bug in cayenne. I have
tried several approaches in order to isolate the direct cause, thinking
it is some kind of misconfiguration in my code, yet no luck.
Using cayenne 3.0, derby (not tested on other db so far).
My cayenne model defines
11 matches
Mail list logo
