Subject | Re: [IBO] TIB_ColumnText and strings that are too long |
---|---|
Author | Martijn Tonies |
Post date | 2006-01-10T17:42:44Z |
Lucas,
How do your users KNOW they defined something in the wrong way.
Will they be checking the 100.000 imported rows?
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com
> Jason Wharton schrieb:I'll have to add my main complaint:
> > I would like to hear from as many people as possible what they think the
> > behavior of IBO should be.
>
> Okay, let's start.
>
> 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 :-)
How do your users KNOW they defined something in the wrong way.
Will they be checking the 100.000 imported rows?
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com