Levente wrote in response to my: >> 3. You have a legacy (relational) database, with extensive reporting >> written for it. Use an ORM. >Relational databases are not legacy, they have features >which "modern" key-value stores don't (and won't). >ORMs may ease the programmer's work, but they >tend to have bad runtime performance >and can't use (all) the features of todays RDBMSs.
In creating the list of different scenarios, I tried to explain in a short text that different needs lead to different solution strategies. Legacy in this context refers to having an existing database you want to continue using. That is a situation where I would recommend starting with ORM unless it is shown that the run-time performance is going to be prohibitive. Please keep in mind that it is a text written for people new to Seaside (and possibly Smalltalk). If you have a suggestion for a better text, please mail me. Stephan Eggermont _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
