From: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | <wheelerj(at)lexmark(dot)com> |
Cc: | <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: Stored Procedure Trouble |
Date: | 2002-04-19 22:13:27 |
Message-ID: | EKEJJICOHDIEMGPNIFIJMEBLHJAA.Inoue@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> -----Original Message-----
> From: wheelerj(at)lexmark(dot)com
>
> I have written a stored procedure in C that opens a file and
> returns it as a
> varchar. The file is 1.5M in size. I then execute the stored
> procedure with
> the following SQL.
>
>
> SELECT name, GetFile() AS Test FROM dummy WHERE name = 'One';
>
>
> When I do this on my Unix system via the Perl DBI it works perfectly.
>
> When I do the same on my Windows machines via Borland C++ Builder and
> the ODBC driver, two things go wrong.
>
> 1) The Query object used to invoke the SQL indicates that no records were
> returned.
>
> This seems to be a problem when any stored procedure is trigger
> by a SELECT
> statement
> regardless of the data returned. I have another stored procedure
> that returns
> a single BYTE and it fails in the same manner.
Could you send me the Mylog(Debug) output for the single
BYTE case(not 1.5M case) ?
> 2) The data returned is truncated to 32769 BYTES when it should be 1.5M.
>
> I have tried modifying various settings in the driver, but nothing I have
> changed seems to
> have any effect.
Are you checking *Text as LongVarcChar* option ?
Are you setting *Max LongVarChar* large enough ?
32769 isn't a restriction of the ODBC drvier.
If you are setting the above options properly,
I'm afraid it's a restriction of Borland C++ Builder.
regards,
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2002-04-21 18:53:30 | Re: md5 with odbc connections??? |
Previous Message | wheelerj | 2002-04-19 14:46:34 | Stored Procedure Trouble |