Re: Pizza Example
Date: Mon, 5 Apr 2004 22:06:17 +0200
Message-ID: <c4se16$bm5$1_at_reader08.wxs.nl>
> I see no logic in this. The database need not constrain the size of data
> that is stored and the UI can either constrain it or not, as the
> designer/user see fit. Constraining the database to only store up to a
> particular length means that the database needs to be changed if a new
valid
> value for an attribute arises that is longer than what was anticipated.
The
> UI can permit scrolling to show only a limited number of characters, but
> scroll to show all. A report writer can wrap long values to a certain
width
The value of constraining the length of a field in a database (R or not R)
is
that all applications should work with this length and do not need to work
with a length above it.
Having sensible length's for fields does not hamper using 'normal' names
for things and makes building an application simpler and more sturdy.
The width of a screen is limited, so is the height and allthough some
applications now use a screen larger than 80x25, all databases designed
during that time still function on larger screens.
ben brugman Received on Mon Apr 05 2004 - 22:06:17 CEST