Hi,
No update of a brand new Product object. It should be a create.
An update is only available if you read the Product object first.
If you use long transactions, you must have a cache time (my
experience is: at least the time to complete the transaction).
cache-type set to none means if you read an object this object is
flushed directly, you cannot change any attribute and save it
into the database again. It's probably not useful if you set
cache-type to none.
You can set dirty checking off. It's the mechanism to check any
change on a field within the transaction. If another transaction
changes the field after the start of your own, Castor throws an
exception. (ObjectModified)
I don't think you missing something obvious. But why don't you
want any caching on you're objects ?
Good luck,
Robin Hoogeboom
> hi,
>
> i would like to rephrase my question:
>
> Is it possible to do long transactions without bounded dirty
checking ?
>
> Example:
> Product p = new Product(...);
> db.update(p);
>
> I tried various cache-type and dirty settings but to no avail.
(can someone
> explain what <cache-type>none</cache-type> does ?)
>
> Am i missing something obvious ?
>
> thanks,
> Henning
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
>
--
_____________________________________________________________________
Zon Breedband Family, 2 keer zo snel als alle andere ADSL aanbieders.
Voor maar 34 euro per maand. Bestel nu op www.zonnet.nl/breedband
Tijdelijk gratis modem en geen aansluitkosten!
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
