|Subject||Re: Issues with String Truncation error on insert (FB 2.1 64 bits windows server)|
>Do you really think that he should do this?
> Your problem is still solvable. Simply add another table. Let one table have huge field lengths (CHAR/VARCHAR or BLOB SUBTYPE TEXT) and use this only for imports, then use AFTER INSERT triggers to copy the first few characters of field(s) to the other table (which you in turn use for querying). Variations of this solution includes adding another field rather than table or even another database ('another database' would probably be an overkill and more difficult to implement in triggers).
i do not know what do that system
but why you need to truncate data provided by your customer?
Think abut this system:
1. Customer can put an order for product
and write in order info text:
"I need 200 red boots .. but only if you can send it to me in two days"
2. your system store truncated data
"I need 200 red boots"
3. and you send a request by week
4. what do customer - say "i do not need this now, get it back"