Changes for page Best Practices-Model

Last modified by Theodore Petrosky on 2014/02/20 18:51

From version 27.1

edited by arroz
on 2007/12/20 11:40

Change comment: There is no comment for this version

To version 25.1

edited by arroz
on 2007/12/20 11:33

Change comment: There is no comment for this version

Summary

Page properties

Content

@@ -20,10 +20,6 @@
  * You may be constrained to existing data types. If you are building an WO application on top of an existing database with millions of records, you cannot choose the data types you want to use - you must use the existing ones used by the database. So, you have to tell EOF what types are those, so that it can read and write information to your existing database.
--If you already tried to create a model, by following [[Janine's tutorial>>http://wotutorial.furfly.com/downloads.html]] or so, you know how flexible it can be - and how tedious it is. It shouldn't be needed to choose, for every integer in your model, the data type for it. Or the data type for every primary key. Or the data type for every string. Worse, if you decide you want to use higher precision floats on all your application, or if you want to increase the size of some of the strings you use in your data model, you should be able to change that information on only one place. After all, duplicating code is bad, right? So why can't you do it?
--
--Well, you can! That's what prototypes are for.
--
  eogenerator
  to-many relationships