[AccessD] Normalization discussion

My rule was -- know what's there and accommodate it. Doesn't matter what it
is, as long as you're consistent and remember the possibility is there.

Susan H.


On Fri, Aug 29, 2014 at 4:42 PM, Stuart McLachlan <stuart at lexacorp.com.pg>
wrote:

> A common misunderstanding.
>
> A Boolean takes one bit per field but packed in a byte so 1-8 booleans in
> a table take 1 byte,
> 9016 booleans take 2 bytes etc..
>
> A single character in a text field takes four bytes.
>
> Nulls are useful.   Magic boundary values really complicate aggregate
> functions and should
> be avoided.
>
>
> --
> Stuart
>
> On 29 Aug 2014 at 20:41, James Button wrote:
>
> >
> > Avoid having null fields, use minimum, or maximum values as meaning no
> > entry and boolean (True/False) probably take 2, or 4 bytes where a
> > simple string "Y" or "N"  value is only 1 char and more
> > understandable. Avoid requiring any auto-sequencing to be strictly
> > ascending Create the main entry with a form, then allow that entry to
> > be selected from the database to create the associated detail Also
> > consider timestamps if you need auditing or just ordering of the data
> > entries.
> >
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>