Re: Re: OT: defining DB fields - working towards consistancy...

Howdy!

Abigail-II wrote:
The traditional way of doing such things is to make a table that contains all the domains...

On the other hand, it may be the case that the tables are appropriately normalized (ignoring the physical data types) but the implementation was done with less care than one might like...

yours,
Michael

Comment on Re: Re: OT: defining DB fields - working towards consistancy...

Replies are listed 'Best First'.
Re: OT: defining DB fields - working towards consistancy... by Abigail-II (Bishop) on Jul 16, 2003 at 11:22 UTC
Uhm, no. That would be impossible in any database I know of. If the tables were appropriately normalized there would be exactly one column, in exactly one table that hold the domains. I don't any database were a column can have more than one type, and if there is one, I don't see how you can manage to define multiple types with "less care". Abigail	[reply]