It's not clear to me why in an EAV based system like eZ; why do you need to update the objects at all, just because the class def changed. Only in the case of deleted attributes would you have integrity probs (orphan attributes) and they could be cleaned up either via a separate (cron?) script or at the time of actually saving a new record. To me the new class def should be automatically usable because the system always has to gather the class def in order to assemble the object for editing etc. anyway. -- Luc.
2009/11/9 Gunnstein Lye <[email protected]> > Luc Chase wrote: > > I believe ez systems has a script to safely add new attributes to a class > > which hold a very large number of objects (e.g. to add new attributes to > a > > user class holding 15000 users). Does anyone know where I can find that > > script? > > > > I could go into the DB and re-assign the new attributes from another > class > > but would like to have a look at that script, in case it seems a better > > option. > > See > http://projects.ez.no/ezscriptmonitor > > This contains the most up to date version of the > addmissingattributes.php script, to my knowledge. You don't have to > install the extension to use the script. > > regards, > -- > Gunnstein Lye > Systems engineer > [email protected] | eZ Systems | http://ez.no > -- Luc.
-- Sdk-public mailing list [email protected] http://lists.ez.no/mailman/listinfo/sdk-public
