On Thu, Sep 10, 2009 at 8:50 AM, Jason Vanhoy <[email protected]> wrote: > * Any time you create an object that needs to be stored in a database, and > that object has a parameter that is an object itself (as opposed to a > primitive like a string or integer) that 2nd object should probably get a > new database table and some foreign key relationship will need to be > established to keep the relationship properly defined.
I'm actually not sure that I would 100% agree here. All this data is probably going to end up on a server somewhere eventually, and *there* (on the server) is needs to be setup as a proper normalized database. But for temporary storage in AIR, serializing an object and jamming it into a SQLite database column saves a TON of time. But having said that it is very important to know how to recognize a good use case for this vs a bad one. Regardless though - this object stored should be data - not the view (UI). Totally 100% in agreement there. -Cameron -- Cameron Childress Sumo Consulting Inc http://www.sumoc.com --- cell: 678.637.5072 aim: cameroncf email: [email protected] ------------------------------------------------------------- To unsubscribe from this list, simply email the list with unsubscribe in the subject line For more info, see http://www.affug.com Archive @ http://www.mail-archive.com/discussion%40affug.com/ List hosted by http://www.fusionlink.com -------------------------------------------------------------
