I also have it as you mentioned- I fetch all on load triggered and save all at the same time (please excuse my pseudocode). There are some things, that if they are heavy, I hold off on until they are called.
No I really haven't tried it.. I'm curious though. I bet this is wildly different in various db daemons, etc. For example, if the server is local, obviously if you are using autocommit, etc etc etc.
It just felt creepy wrong to do it that way- but.. maybe the tech is up it these days.. hmm..... What's really cool is that you actually wouldn't be changind the api at all- most of it.. just the internals. So, I could take one of my objects, rename it and rework it to act that way.. hm.. more to come about this sooner or later.
In reply to Re^2: not caching to object in code interface to database?
by leocharre
in thread not caching to object in code interface to database?
by leocharre
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |