in reply to Re: Avoiding Strange Win32::ODBC Return Values for Integers
in thread Avoiding Strange Win32::ODBC Return Values for Integers (NUL)

The output is the same if I just print it - so it is what I get from ODBC already.
I just checked the SQL Server table properties again - I really do a sum() over a field defined as int.
  • Comment on Re^2: Avoiding Strange Win32::ODBC Return Values for Integers

Replies are listed 'Best First'.
Re^3: Avoiding Strange Win32::ODBC Return Values for Integers
by thor (Priest) on Oct 28, 2005 at 15:06 UTC
    So you're saying that you get a 57 with some strange character after it when you just print it as text?

    thor

    Feel the white light, the light within
    Be your own disciple, fan the sparks of will
    For all of us waiting, your kingdom will come

      That is right - I just wrote it to a file to be able to paste it, but pasting did not work from TextPad.
      It tells me: can not copy... containing null (code=0) characters.
      Notepad.exe does not show it nor complain, but also only shows a space when pasting it.

      Update: It looks like 57.00[] while [] denotes the strange last character.

      Thanks,
      jonix
        I don't know why you're getting a NUL (ASCII character 0) in your output, but here's how we can get rid of it:
        my $nul = chr(0); $value =~ s/$nul//g;
        I would suggest that for all of the values coming out of the database; it's pretty likely that you don't want NULs in your output.

        thor

        Feel the white light, the light within
        Be your own disciple, fan the sparks of will
        For all of us waiting, your kingdom will come