Subject | Re: [IBO] TIB_ColumnText and strings that are too long |
---|---|
Author | Svein Erling Tysvær |
Post date | 2006-01-11T08:16:33Z |
Basically, this doesn't cause me any problems - I don't mind if
surnames like "van der Wonderbaum-Stockholm" (I doubt that's an
existing surname) are truncated - not to mention when doing
UPDATE <table>
SET FullName = Surname || ' ' || FirstName
when the definitions are
FullName = VARCHAR(64)
Surname = VARCHAR(32)
FirstName = VARCHAR(32)
Though if I (hypothetically) implemented my own password scheme and a
user decided to use the password "firebirdIsaDecentdataBase" and the
field was limited to eight characters, I guess an exception would be
required. Hence, a column attribute with the default behaving as it
does today would - in my opinion - be good. That is: if the SQL
standard says something about the matter, I guess whatever it says
would be the most appropriate default behaviour.
Set
surnames like "van der Wonderbaum-Stockholm" (I doubt that's an
existing surname) are truncated - not to mention when doing
UPDATE <table>
SET FullName = Surname || ' ' || FirstName
when the definitions are
FullName = VARCHAR(64)
Surname = VARCHAR(32)
FirstName = VARCHAR(32)
Though if I (hypothetically) implemented my own password scheme and a
user decided to use the password "firebirdIsaDecentdataBase" and the
field was limited to eight characters, I guess an exception would be
required. Hence, a column attribute with the default behaving as it
does today would - in my opinion - be good. That is: if the SQL
standard says something about the matter, I guess whatever it says
would be the most appropriate default behaviour.
Set
--- In IBObjects@yahoogroups.com, "Jason Wharton" wrote:
> I would like to hear from as many people as possible what they think
> the behavior of IBO should be.
>
> Should IBO raise an exception if there is a text assignment that is
> longer than there is storage for it.