"Leslie P. Polzer" <[email protected]> writes: > Daniel Brooks wrote: >> >> This may have been asked before, but I find I'm in need of some more >> information about the intended way of giving all the objects I'm storing >> a unique ID. This might be purely a cl-prevelance question though. >> >> I'm deriving my objects from cl-prevelance's object-with-id class, and >> I've overridden class-id-slot-name so that weblocks can figure out the >> id of the objects I'm storing and retrieving. However, everything has an >> id of -1, which is obviously wrong. Has anyone seen this before? Am I >> skipping a step? From what I could tell, cl-prevelance should be doing >> all the work for me, keeping the next available id stored in it's >> database somewhere, but it doesn't seem to be doing so. > > From the Prevalence sources: > > (defclass object-with-id () > ((id :reader get-id :initarg :id :initform -1)) > (:documentation "Superclass for objects with an id")) > > Weblocks assigns an uid when you call PERSIST-OBJECT. > > Leslie
And apparently the form view is calling that from update-object-view-from-request, right? The objects are certainly being persisted; any new objects that I try to create end up overwriting the first (because they have the same id.) db48x --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
