Cool, fast reply :) So u r around here ;)
Here some wrong things:
- miss the support new UFT8 charset
- while i use character set with more than 1 bite for char(unicode_fss/utf8 for ex), i have this strage behavior.
When i edit a field of a table(or simpli a stored procedure parameter with explicit char-set), the size of the field/parameter is wrong, with unicode_fss is X3(for exaple, 30 instead of 10).
- when i edit a stored procedure with a paramenter "Blob sub_type 1", the "sub_type 1" miss then when i recompile it the parameter is of a different type (this thing is important because many tools (my ones too :D ) need to know the exactly type of the parameter, in this case bin or text).
correcting this things will be a very good start i think.
tx & cya
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi :)
Marathon don't work with fb2: Ryan, do you plan to support it?
tx a lot! :)
bye
There are plans to support FB2 but I haven't had anytime to spend on it in the last month or so. Can you tell me what doesn't work specifically?
Ryan.
Cool, fast reply :) So u r around here ;)
Here some wrong things:
- miss the support new UFT8 charset
- while i use character set with more than 1 bite for char(unicode_fss/utf8 for ex), i have this strage behavior.
When i edit a field of a table(or simpli a stored procedure parameter with explicit char-set), the size of the field/parameter is wrong, with unicode_fss is X3(for exaple, 30 instead of 10).
- when i edit a stored procedure with a paramenter "Blob sub_type 1", the "sub_type 1" miss then when i recompile it the parameter is of a different type (this thing is important because many tools (my ones too :D ) need to know the exactly type of the parameter, in this case bin or text).
correcting this things will be a very good start i think.
tx & cya
Can you log these in under the bug tracker? That way I'll be able to track them and as I fix them you'll be able to monitor my progress.
Ryan.
Done.
Tx a lot :)