Child pages
  • Best Practices-Model

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • There are some things EOF simply can't guess. If you have a String, you need to decide how much space you want to use on the database for it. If you know the String will contain a color, like "Red" or "Yellow", something like a varchar 50 should be enough. On the other end, if the String will be used to store a full name of a user, you probably want to make it a varchar 1000 or so (European names can be very long!). Of course, most databases allow you to use unlimited text data types, but that has serious implications in the database speed. So, it's up to you.
  • YMMV however, Postgresql recommends that you use a column of type text. Their documentation states there is no speed penalty for choosing this over varchar(some number). The Entity Modeler prototype is 'longText'
  • 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.