problem with compound primary key when one key=

hi, i found a problem with using a compound primary key (two columns). it appears only if one of the keys is set to (an empty string, NOT null). here's my setup: ojb 1.0.1, mysql 4.0.23 on XP prof., jdk 1.4.2_07 repository.xml: class-descriptor

Re: problem with compound primary key when one key=

hi günter, could you please post the sql ? is there a row in the database with locale= ? i'm asking this because you say that you can insert it manually. btw. it's no longer necessary to use ids in field-descriptors. jakob Günther Wieser schrieb: hi, i found a problem with using a compound

Re: problem with compound primary key when one key=

Hi Günther, maybe the broker does something unexpected with the empty string? any ideas? When storing an object with PB.store(obj), OJB has to decide if an insert or update is required. Thus if the PK field is of type String and the value is 'null' or an empty String, OJB assume that the PK

AW: problem with compound primary key when one key=

, guenther -- Günther Wieser creative-it Guglgasse 6/1/11/1 A-1110 Wien Austria http://www.creative-it.com -Ursprüngliche Nachricht- Von: Armin Waibel [mailto:[EMAIL PROTECTED] Gesendet: Montag, 28. Februar 2005 20:29 An: OJB Users List Betreff: Re: problem with compound primary key when

Re: AW: problem with compound primary key when one key=

. Februar 2005 20:29 An: OJB Users List Betreff: Re: problem with compound primary key when one key= Hi Günther, maybe the broker does something unexpected with the empty string? any ideas? When storing an object with PB.store(obj), OJB has to decide if an insert or update is required. Thus

Re: AW: problem with compound primary key when one key=

Betreff: Re: problem with compound primary key when one key= Hi Günther, maybe the broker does something unexpected with the empty string? any ideas? When storing an object with PB.store(obj), OJB has to decide if an insert or update is required. Thus if the PK field is of type String

Re: AW: problem with compound primary key when one key=

List Betreff: Re: problem with compound primary key when one key= Hi Günther, maybe the broker does something unexpected with the empty string? any ideas? When storing an object with PB.store(obj), OJB has to decide if an insert or update is required. Thus if the PK field is of type String

Re: AW: problem with compound primary key when one key=

Austria http://www.creative-it.com -Ursprüngliche Nachricht- Von: Armin Waibel [mailto:[EMAIL PROTECTED] Gesendet: Montag, 28. Februar 2005 20:29 An: OJB Users List Betreff: Re: problem with compound primary key when one key= Hi Günther, maybe the broker does something unexpected

AW: AW: problem with compound primary key when one key=

this topic), seems very reasonable. kr and many thanks, guenther -Ursprüngliche Nachricht- Von: Armin Waibel [mailto:[EMAIL PROTECTED] Gesendet: Montag, 28. Februar 2005 20:56 An: OJB Users List Betreff: Re: AW: problem with compound primary key when one key= Günther Wieser wrote: hmm