On Wed, Jun 30, 2010 at 5:37 PM, Steve Hurst
wrote:
> Hi all, not sure if this is a bug or user error - any insight appreciated!
>
> I have a schema that defines a two column primary key on a table - the docs
> indicate this will create a unique composite key. However, code running
> "INSERT OR R
ah, sorry ...
Am 01.07.2010 09:49, schrieb Jan:
> Which row (node_id, attribute) is not unique?
>
> Jan
>
> Am 30.06.2010 23:37, schrieb Steve Hurst:
>> Hi all, not sure if this is a bug or user error - any insight appreciated!
>>
>> I have a schema that defines a two column primary key on a table
Which row (node_id, attribute) is not unique?
Jan
Am 30.06.2010 23:37, schrieb Steve Hurst:
> Hi all, not sure if this is a bug or user error - any insight appreciated!
>
> I have a schema that defines a two column primary key on a table - the docs
> indicate this will create a unique composite
Hi all, not sure if this is a bug or user error - any insight appreciated!
I have a schema that defines a two column primary key on a table - the docs
indicate this will create a unique composite key. However, code running
"INSERT OR REPLACE INTO ..." many times over a long period of time event
4 matches
Mail list logo