Mailing-List: contact ojb-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "OJB Users List" <ojb-user@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <42B6906A.2060004@apache.org>
Date: Mon, 20 Jun 2005 11:46:18 +0200
From: =?ISO-8859-1?Q?Martin_Kal=E9n?= <mkalen@apache.org>
Organization: ASF
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: OJB Users List <ojb-user@db.apache.org>
Subject: Re: primary key problem sql server
References: <59f42c0005061504004dacea21@mail.gmail.com>
In-Reply-To: <59f42c0005061504004dacea21@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Alessandro Colantoni wrote:
> I'm using ojb 1.0.1 with sql server.
>  When I store an object, and then I delete it directly on the db I can't 
> insert it a second time.
>  Before storing I use to check if an object with the same key exists.
> ojb doesn't detect any object with the same key (correctly... I deleted it)
> But when storing it catch a sql server exception because primary key already 
> exists.
> Is it a limit of microsoft sql server (it keeps primary key somewhere?) or 
> I'm doing something wrong?

This sounds like a transaction isolation problem. If you use the PB API with
OJB without the two-level cache you will not have any transaction isolation
and a delete will be directly visible in the cache before commit.

However, if you don't use auto-commit on the Connection to MSSQL the database
DELETE will not be performed until COMMIT.

What is your auto-commit setting in repository_database.xml and which OJB API
are you using?

Regards,
  Martin


---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org