As of version 17, DBISQL by default uses the machine's locale to display dates and numbers in the according locale, as stated here.

For locales with comma as decimal separator, DBISQL uses the semicolon as default field separator. This works fine in my case with German locale.

However, DBISQL does not accept numbers with a decimal comma as input (say, "0,75") for floating point or decimal data with the INPUT statement but raises a SQLCODE -151 error:

Cannot convert '0,75' to double.

This somewhat does make it still difficult to import localized numbers. I suspect I still have to load those numbers into dummy string columns and then have to turn their values – swapping decimal comma to decimal point – into "real numbers".

Am I missing a point (pun intended)?

asked 05 Jan, 13:01

Volker%20Barth's gravatar image

Volker Barth
accept rate: 34%

edited 05 Jan, 13:07

Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 05 Jan, 13:01

question was seen: 156 times

last updated: 05 Jan, 13:07