Thread: [INTERFACES] C++ Builder (Delphi), ODBC and large objects

[INTERFACES] C++ Builder (Delphi), ODBC and large objects

From
"angg"
Date:
David Hartwig (DH) wrote:
ANGG wrote:

ANGG>> 1 Does anybody use large objects with C++ Builder (Delphi), BDE,
ODBC,
ANGG>> PostgreSQL?

DH>Yes, occasionally - without any problem.

WHO?!!! Answer me, please (the problem makes me trow out half a year's work
as useless garbage)

DH>Have you seen
DH> http://www.insightdist.com/psqlodbc/psqlodbc_faq.html#largeobjects

Yes, I create large object as it reccomends
create type lo

    internallength=4,  externallength=10,
    input=int4in, output=int4out,
    default='',  passedbyvalue
);
and have all the problems I say here about.

By the way, PostgreSQL's man create_type recommends another way to create
the large object type:
create type bigobj (
  input = lo_filein,
  output = lo_fileout,
  internallength = variable
);

Can anybody tell me how should I implement lo_filein and lo_fileout in this
case?

Thank you, Mikhail.





Re: [INTERFACES] C++ Builder (Delphi), ODBC and large objects

From
Sergio
Date:
Hi,
I have another problem with lo, I used the new Insight Odbc
driver and when I try to use the datapump utility of Borland
(Delphi) to migrate paradox tables, when it try to convert
memo fields to large objects it gave an error, wich NOT
happen with the previous version of the driver.
I resolved changing the type of the target field to
varchar.

Btw, any plans to support scrollable cursors and ODBC 3
from Insight ?

TIA,
Sergio Kessler

PS: rh5.1, Psql 6.3.2 and win odbc driver from this month.


Re: [INTERFACES] C++ Builder (Delphi), ODBC and large objects

From
Byron Nikolaidis
Date:

Sergio wrote:

> Hi,
> I have another problem with lo, I used the new Insight Odbc
> driver and when I try to use the datapump utility of Borland
> (Delphi) to migrate paradox tables, when it try to convert
> memo fields to large objects it gave an error, wich NOT
> happen with the previous version of the driver.
> I resolved changing the type of the target field to
> varchar.
>

I haven't had any success figuring out why Borland products can't write
blobs.  Maybe you could send me logfiles of the problems (both sql.log
and psqlodbc.log).

> Btw, any plans to support scrollable cursors and ODBC 3
> from Insight ?

I don't see any real need to support ODBC 3.0.  This would be quite an
involved project for very little gain as far as I can tell.  The driver
manager seems to do a good job of down converting the 3.0 calls to
2.0.   Is there something specific in 3.0 that you need or something?

As for scrollable cursors, "static" scrollable cursors are already
supported.   If you want positioned update/delete, the driver can work
with the odbc cursor library to achieve that.  As for dynamic or keyset
cursors, I had plans to implement a mixed keyset cursor (similar to what
the Jet engine does), but time is a problem.

Byron




Re: [INTERFACES] C++ Builder (Delphi), ODBC and large objects

From
Sergio
Date:
Byron Nikolaidis <byronn@insightdist.com> el d�a Wed, 21 Oct 1998 17:53:13
-0400, escribi�:

>
>
>Sergio wrote:
>
>> Hi,
>> I have another problem with lo, I used the new Insight Odbc
>> driver and when I try to use the datapump utility of Borland
>> (Delphi) to migrate paradox tables, when it try to convert
>> memo fields to large objects it gave an error, wich NOT
>> happen with the previous version of the driver.
>> I resolved changing the type of the target field to
>> varchar.
>>
>
>I haven't had any success figuring out why Borland products can't write
>blobs.  Maybe you could send me logfiles of the problems (both sql.log
>and psqlodbc.log).

I don't have the files with me right now, I will try tomorow.
But the strange thing is that it not happen with the previous driver.

>> Btw, any plans to support scrollable cursors and ODBC 3
>> from Insight ?
>
>I don't see any real need to support ODBC 3.0.  This would be quite an
>involved project for very little gain as far as I can tell.  The driver
>manager seems to do a good job of down converting the 3.0 calls to
>2.0.   Is there something specific in 3.0 that you need or something?

Well, I have a couple of delphi componentes that talk directly
to the driver bypassing the BDE (because I hate to distribute the BDE),
and it say is for Odbc 3.
See the attachments, I've managed to convince the author to release
the source in the next version :)

>As for scrollable cursors, "static" scrollable cursors are already
>supported.   If you want positioned update/delete, the driver can work
>with the odbc cursor library to achieve that.  As for dynamic or keyset
>cursors, I had plans to implement a mixed keyset cursor (similar to what
>the Jet engine does), but time is a problem.

The same here, all the components (Odbc98, OdbcExpress) expect (or work
better with) scrollable cursors in the driver, but I guess I can live
with this.

Cheers,
Sergio Kessler

Attachment

Re: [INTERFACES] C++ Builder (Delphi), ODBC and large objects

From
Sergio
Date:
Byron Nikolaidis <byronn@insightdist.com> el día Wed, 21 Oct 1998 17:53:13
-0400, escribió:

>
>
>Sergio wrote:
>
>> Hi,
>> I have another problem with lo, I used the new Insight Odbc
>> driver and when I try to use the datapump utility of Borland
>> (Delphi) to migrate paradox tables, when it try to convert
>> memo fields to large objects it gave an error, wich NOT
>> happen with the previous version of the driver.
>> I resolved changing the type of the target field to
>> varchar.
>>
>
>I haven't had any success figuring out why Borland products can't write
>blobs.  Maybe you could send me logfiles of the problems (both sql.log
>and psqlodbc.log).

I don't have this files with me right now.

>> Btw, any plans to support scrollable cursors and ODBC 3
>> from Insight ?
>
>I don't see any real need to support ODBC 3.0.  This would be quite an
>involved project for very little gain as far as I can tell.  The driver
>manager seems to do a good job of down converting the 3.0 calls to
>2.0.   Is there something specific in 3.0 that you need or something?

Well, I have a freeware components (mOdbc) that talk to the odbc
directly bypassing the BDE (because I hate to distribute the BDE)
but it is made for 3.0 drivers, if you want this comps, just tell me.
Btw, I've managed to convince the author to release the source
code :)

>As for scrollable cursors, "static" scrollable cursors are already
>supported.   If you want positioned update/delete, the driver can work
>with the odbc cursor library to achieve that.  As for dynamic or keyset
>cursors, I had plans to implement a mixed keyset cursor (similar to what
>the Jet engine does), but time is a problem.

The same happen here, all 3 party components want (or work better with)
dynamic scrollable cursors, I'm talking about odbc98
(http://www.odbc98.com) or OdbcExpress (http://www.odbcexpress.com),
but maybe I choose mOdbc.

Cheers,
Sergio