|
From: Peter G. <pe...@fs...> - 2004-03-08 19:23:58
|
> It's not a very general purpose solution though. I like the idea of having a > kind of "update object" which looks like an SQLObject, and can be shoved > back into the database when it's finished being updated. It would be > especially handy if it was picklable, so that it could be used as a Webware > session variable. When I have made more "light" object models on relational databases I have always used generated unique IDs, generally 256-bit md5 sums generated on pesudo-random data. This way I was always ID's would always look the same no matter what database I used. Either this sort of IDs can be used or the ID simply cannot be retrieved from a memory-only SQLObject. /P |
