[Seaside] Equivalent of unique keys in a persistent object model ?

Chris Muller asqueaker at gmail.com
Sun Jan 17 20:02:31 UTC 2010

To me, "sequence #'s" usually implies numeric and consecutive, but you
only mentioned using them for unique identifiers.  UUID (Universally
Unique Identifier) can also be useful, if a little heavier than
integral id's.  Otherwise, Magma has has integral, consecutive
sequence # generators.

Often, however, "record identifiers" can be eliminated when moving to
an object system, since objects have direct references to other


On Sun, Jan 17, 2010 at 9:51 AM,  <recursive68 at gmail.com> wrote:
> Hi,
> I'm a newby to ST and Seaside. I attempting to port web app that's written
> in Oracle/Java over to Seaside running on Pharo. The current application
> uses Oracle sequence generated unique id's for unique identifiers for
> records, is there a parallel to this when using just objects persisted in
> the Pharo image ? I know I can code my one implementation to replicate this
> but wondered whether this is the best way to model it, what are the
> alternatives and if it is the best way, is there a ready made package that I
> could use to generate unique id's ?
> Jon
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list