Unless something has changed in the past few months, the answer is yes. Certain functions, such as quickforms, create persistent objects but assume they will be GC'ed unless they are explicitly persisted (the CL-SQL model). There are intentions to remove this requirement, but I don't think that's been done yet.
In the meantime you can look at what I did with the elephant backend to use auto-created proxy classes for the places in weblocks where temporary objects are needed. Proxies are upgraded to newly-created actual persistent classes when persist-object is called. Let me know if you have questions about what I did; it's a fairly small set of code and small method hooks into the weblocks framework. Ian On Apr 2, 2009, at 8:16 AM, Antek wrote: > > I'm writing store backend to cl-perec (http://common-lisp.net/project/ > cl-perec/). My question is, does a store have to guarantee, that > objects won't be persisted until persist-object is called. By default > cl-perec makes all objects persistent, so all changes in the objects > are automatically commited with the transaction. > > So, is it safe or does weblocks create any temporary objects which it > doesn't expect to be saved. > > Thanks. > Antoni > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
