Tobias Schlitt wrote: > Hi fellow ezc'ers! > > First of I wish you merry X-mas! :) > > Second I added a design draft for enhancement #010913 "Complex data > types (e.g. DateTime) for PersistentObject" [1] right before christmas > and already started implementing it (as the main design was already > fixed during the last summer conference and noted in the issue). Please > take a look at PersistentObject/design/design-1.4.txt (last section) and > state any comments here.
It looks ok to me. One question I have is how would you handle complex conversions, for example currency conversions where you have to keep the currency and date of exchange in the database? Are more arguments needed for fromDatabase() and toDatabase()? > Beside this request for review, I'd like to discuss a naming issue with > you. So far I named the interface for data type conversions > "ezcPersistentObjectPropertyConversion", because the classes > implementing it will perform a conversion. By now I think this name > sounds kinda strange and should actually be > "ezcPersistentObjectPropertyConverter" instead. What do you think? I like the first name better, but for interfaces we are using names similar to the second one (eg. ezcConfigurationReader, ezcFeedParser, ezcDocumentConverter, etc). -- Alexandru Stanoi eZ Components System Developer eZ Systems | http://ez.no -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
