I'm not talking about DB constiency. I'm talking about data consistency.
And I'm not talking about multi-threading. OJB is a tool for accessing the
database. If it degrades the quality/reliablity/constency of the data,
it's value is pretty much 0. Since I do all my data access through OJB, if
it won't be return consistent data, then the fact that data in the database
is consistet is irrelevant.
David
|---------+--------------------------->
| | Oki DZ |
| | <[EMAIL PROTECTED]|
| | m> |
| | |
| | 04/03/2003 07:04|
| | PM |
| | Please respond |
| | to "OJB Users |
| | List" |
| | |
|---------+--------------------------->
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: OJB Users List <[EMAIL PROTECTED]>
|
| cc:
|
| Subject: Re: StackOverflow
|
|
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
On Thu, Apr 03, 2003 at 04:07:40PM -0500, [EMAIL PROTECTED] wrote:
> The problem isn't there if you don't say refresh, but in that
> case, OJB doesn't produce reliable/consistent data.
Question is, can we expect that consistency is the responsibility of
OJB? I think db consistency should be done at the db level (using
triggers).
Oki
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
