Subject | Re: [IBO] TIB_ColumnText and strings that are too long |
---|---|
Author | Lucas Franzen |
Post date | 2006-01-10T17:24:56Z |
Jason Wharton schrieb:
I'm quite glad that IBO does this, so I don't have to do it all the time
(as I had to in pre-IBO times).
Example:
Users can define interfaces in my program where they define the fields
within a textfile, at which position which field is in which length.
Of course there is a maximum length that's defined by the underlying
table field (and shown to the user), but if they define it longer than
that then it's their fault ;-) and the interface object that's handling
the data is doing nothing than reading the file, parsing it according to
the defined structure and assigning the value to the matching TIB_DSQL
parameter.
Not only by this I'm quite happy with the way IBO does work - it keeps
me from doing a copy ( ) on Varchar parameters before executing a
statement...
Keep it the way it is, otherwise I go crazy :-)
Luc.
> I would like to hear from as many people as possible what they think theOkay, let's start.
> behavior of IBO should be.
I'm quite glad that IBO does this, so I don't have to do it all the time
(as I had to in pre-IBO times).
Example:
Users can define interfaces in my program where they define the fields
within a textfile, at which position which field is in which length.
Of course there is a maximum length that's defined by the underlying
table field (and shown to the user), but if they define it longer than
that then it's their fault ;-) and the interface object that's handling
the data is doing nothing than reading the file, parsing it according to
the defined structure and assigning the value to the matching TIB_DSQL
parameter.
Not only by this I'm quite happy with the way IBO does work - it keeps
me from doing a copy ( ) on Varchar parameters before executing a
statement...
Keep it the way it is, otherwise I go crazy :-)
Luc.