dj_ryan, el martes 1 de noviembre a las 06:39 me escribiste:
>
> I find SQLObject very limited and it kind of makes me sad - I'm used to
> using Hibernate.
>
> Small example: Why do property updates immediately execute UPDATE ?!
> What if we rollback the transaction? Wasted call. why not flush
> updates on commits?
You can use lazy updates for that.
> Right now I kind of feel like SQLObject is someone's pre-alpha
> technology preview. I'm looking to using TG for stats and reporting on
> an existing database, and I think I'm going to skip SQLObject.
Yes, you should, SQLObject is not designed (AFAIK) for stats and reports.
--
LUCA - Leandro Lucarella - JID: luca(en)lugmen.org.ar - Debian GNU/Linux
.------------------------------------------------------------------------,
\ GPG: 5F5A8D05 // F8CD F9A7 BF00 5431 4145 104C 949E BFB6 5F5A 8D05 /
'--------------------------------------------------------------------'
Agitamos toda la zona de la paleta al horno, vemos que una luz nos
atraviesa toda la zona intestinal...
-- Sidharta Kiwi
