stored procs string fields
Posted: Mon 28 Jun 2021 05:37
Hi,
I have a table where some varchar fields are of character type utf and some are ascii.
When I do a stored proc which returns a parameter which is a varchar(5) ASCII (defined as domain for field) half of the characters are 3 of 5 characters are cut off - me suspecting - because the ide creates a widestring field instead of a string field I guess???
If I make the parameter for the returning string a s STRING field the value is correct.
I have version 6 of the data access components (Delphi ria 10.3.1) and cannot upgrade to 7.4 because it asks for delphi to be 10.3.3. (which is difficult to upgrade for me)
Now if I did manage to upgrade would the component 7.4 get the appropriate field for the string parameter e,g, widestring if field is utf8 and string if field is ASCII or none e.g. a one byte character?
Or is my suspicion of why the data gets cut off wrong altogether and there is a different reason. when I make the parameter a string field the returned value is CORRECT which leads to my assumption.
Will this be fixed at some stage or is it fixed already in a newer version etc.
thanks
sigi
I have a table where some varchar fields are of character type utf and some are ascii.
When I do a stored proc which returns a parameter which is a varchar(5) ASCII (defined as domain for field) half of the characters are 3 of 5 characters are cut off - me suspecting - because the ide creates a widestring field instead of a string field I guess???
If I make the parameter for the returning string a s STRING field the value is correct.
I have version 6 of the data access components (Delphi ria 10.3.1) and cannot upgrade to 7.4 because it asks for delphi to be 10.3.3. (which is difficult to upgrade for me)
Now if I did manage to upgrade would the component 7.4 get the appropriate field for the string parameter e,g, widestring if field is utf8 and string if field is ASCII or none e.g. a one byte character?
Or is my suspicion of why the data gets cut off wrong altogether and there is a different reason. when I make the parameter a string field the returned value is CORRECT which leads to my assumption.
Will this be fixed at some stage or is it fixed already in a newer version etc.
thanks
sigi