Changes

Internal:Data Modelling Practices

1,275 bytes added, 10:39, 10 July 2015
Created page with "=== What data type should be used if the property values can be accurately defined. === Always try to use the actual data type, of the value which should be stored, for the pr..."
=== What data type should be used if the property values can be accurately defined. ===
Always try to use the actual data type, of the value which should be stored, for the property. For example, if a date value is entered the data type should be DateTime.

=== What data type should be used if the property values are basically unknown. ===
Still, try to use the most suitable data type. For example, for a numeric value it could be double, which takes integer as well as floating point numbers.
If the values might be alphanumeric, use type string.

=== Language specific date / time settings and string manipulation methods. ===
Be aware that the date and time formats always depend on the system's language settings. There will be a difference on servers running an English and German operating system.
Hence, do not use any string manipulation methods to extract the year, month, day,... of a date value. Use C# methods, like <code>DateTime.Year(), DateTime.Month()</code> instead to get the proper value.

=== Get the login and date/time when a value has been changed. ===
Enable ''NEEDSVALIDATION'' on the property, such that the client (system) automatically stores the login and date/time information.

[[Category:Best Practices (internal)|Data Modelling Practices]]
10,686
edits