There is a ticket open for this yet.
[]s
Carlos
http://www.firebirdnews.org
FireBase - http://www.FireBase.com.br
| Many error messages are not enough descriptive for the application's developer. By example, when trying to save a row: "data truncated" is not enough. We have no idea which is the field problematic and the table can have 20, 30, 40 or more fields. So, we need to look each field, one for one, until hours later find the evil field. The experienced developer of course can find the error fastly, but for begginers it is a headache. The ideal would be can identify fastly the record and the field that are having problems. Greetings. Walter. On Thu, Mar 6, 2014 at 12:39 PM, Alex Peshkoff <peshk...@mail.ru> wrote: On 03/06/14 20:31, Dimitry Sibiryakov wrote: > 06.03.2014 17:25, Alex Peshkoff wrote: >> I must say that with correctly working Sqlda->BLR converter > Actually, this is exactly thing that I'm going to kill. > Yes, as soon as we stop to call BLR-oriented functions to implement SQLDA-oriented API calls converting Sqlda->BLR->IMessageMetadata instead Sqlda->IMessageMetadata directly makes absolutely no sense. |
------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
