Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2012-03

Database questions re 21579: [Patch] Dbtestframework compilationf fixes for Win64

8 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Reinier Olislagers

Hi list,

I've submitted a patch (21579) to allow win64 dbtestframework compilation. It does that by disabling support for some databases.

Oracle, PostgreSQL, MS SQL Server and Sybase connectors are not built on Win64: see
packages\fcl-db\src\sqldb\postgres\fpmake.pp

Speculated with Lacak2 in mantis issue. I suspected they're disabled because of lack of driver/client support.
Searched through FPC and FPC dev lists on Oracle 64 and found nothing..

If lack of driver/client support was the reason, the current situation may have changed:
PostgreSQL 9 has support for Windows x64, e.g.
http://www.enterprisedb.com/products-services-training/pgbindownload

Oracle instant client for Windows x64 (the download size makes it... not so instant though)
http://www.oracle.com/technetwork/database/features/instant-client/index-097480.html

FreeTDS can, at least in theory, be compiled for Windows 64 bit systems. This covers MS SQL Server and Sybase.

I'll leave the patch as is, unless driver support was the issue, in which case it might make sense to re-enable these connectors...

Thanks,
Reinier

Reply by email

Sven Barth
to Reinier Olislagers
Reinier Olislagers wrote
Oracle instant client for Windows x64 (the download size makes it... not so instant though) http://www.oracle.com/technetwork/database/features/instant-client/index-097480.html

It's called "instant" client, because it does not need any installation compared to the "usual" client.

Note: I had yet no real success with the Oracle connection on Windows (32 Bit). I'm still investigating the exact reasons, so I can report approbiate bugs (one reason seems to be that the calling convention in the oracle interface unit is wrong).

Regards,
Sven

Reply by email

Reinier Olislagers
to Sven Barth
Sven Barth wrote 6 lines
Am 28.03.2012 10:29, schrieb Reinier Olislagers: > Oracle instant client for Windows x64 (the download size makes it... not > so instant though) > http://www.oracle.com/technetwork/database/features/instant-client/index-097480.html It's called "instant" client, because it does not need any installation compared to the "usual" client.

I know, don't get me started on ORACLE_HOME etc...

Do you know why it's not compiled on Win64?

Note: I had yet no real success with the Oracle connection on Windows (32 Bit). I'm still investigating the exact reasons, so I can report approbiate bugs (one reason seems to be that the calling convention in the oracle interface unit is wrong).

Can't remember whether I've tried running it at all... But since it has been committed surely it must have been working for at least some people!??!

Reply by email

Sven Barth
to Reinier Olislagers
Reinier Olislagers wrote 10 lines
On 28-3-2012 11:04, Sven Barth wrote: > Am 28.03.2012 10:29, schrieb Reinier Olislagers: >> Oracle instant client for Windows x64 (the download size makes it... not >> so instant though) >> http://www.oracle.com/technetwork/database/features/instant-client/index-097480.html > It's called "instant" client, because it does not need any installation > compared to the "usual" client. I know, don't get me started on ORACLE_HOME etc... Do you know why it's not compiled on Win64?

Do you want the reason why it's not compiled in the view of fpmake (a) or in a technical view (b)?

(a) No wonder as the OS list for Oracle is
"SqldbConnectionOSes-SqldbWithoutPosgresOSes"

(b) Maybe nobody needed it yet. I myself might be the first one at all who wanted to interface with Oracle on Windows directly without ODBC. ;)

Show quoted text 6 lines
> Note: I had yet no real success with the Oracle connection on Windows > (32 Bit). I'm still investigating the exact reasons, so I can report > approbiate bugs (one reason seems to be that the calling convention in > the oracle interface unit is wrong). Can't remember whether I've tried running it at all... But since it has been committed surely it must have been working for at least some people!??!

Maybe it was only really tested on Linux...

Regards,
Sven

Reply by email

Reinier Olislagers
to Sven Barth
Sven Barth wrote 7 lines
Am 28.03.2012 11:12, schrieb Reinier Olislagers: > On 28-3-2012 11:04, Sven Barth wrote: >> Am 28.03.2012 10:29, schrieb Reinier Olislagers: > Do you know why it's not compiled on Win64? Do you want the reason why it's not compiled in the view of fpmake (a) or in a technical view (b)?

(b): (a) is already mentioned in my bug report and my mail to this list...

(b) Maybe nobody needed it yet. I myself might be the first one at all who wanted to interface with Oracle on Windows directly without ODBC. ;)

<snip>

Maybe it was only really tested on Linux...

Mmm... could be...

Thanks Sven, if I get no other answers I think I'll propose a patch that builds Oracle, PostgreSQL, MSSQL and Sybase on Win64...

Thanks,
Reinier

Reply by email

Reinier Olislagers
to Reinier Olislagers
Reinier Olislagers wrote 11 lines
On 28-3-2012 11:36, Sven Barth wrote: > Am 28.03.2012 11:12, schrieb Reinier Olislagers: >> On 28-3-2012 11:04, Sven Barth wrote: > (b) Maybe nobody needed it yet. I myself might be the first one at all > who wanted to interface with Oracle on Windows directly without ODBC. ;) <snip> > Maybe it was only really tested on Linux... Mmm... could be... Thanks Sven, if I get no other answers I think I'll propose a patch that builds Oracle, PostgreSQL, MSSQL and Sybase on Win64...

On second thoughs: I don't have any need to have these components on x64 Windows and have other priorities (e.g. I'd prefer seeing a working dbtestframework on Win64 so Firebird embedded etc can get properly tested), so I think I'll pass on that patch for now.

So... if anybody (like Michael Van Canneyt ;) ) would apply 21579, I'd be grateful...

Thanks again Sven for you time & answer,

regards,
Reinier

Reply by email

LacaK
to Reinier Olislagers

Reinier Olislagers wrote / napísal(a):

Show quoted text 27 lines
On 28-3-2012 12:22, Reinier Olislagers wrote: > On 28-3-2012 11:36, Sven Barth wrote: > >> Am 28.03.2012 11:12, schrieb Reinier Olislagers: >> >>> On 28-3-2012 11:04, Sven Barth wrote: >>> >> (b) Maybe nobody needed it yet. I myself might be the first one at all >> who wanted to interface with Oracle on Windows directly without ODBC. ;) >> > <snip> > >> Maybe it was only really tested on Linux... >> > Mmm... could be... > > Thanks Sven, if I get no other answers I think I'll propose a patch that > builds Oracle, PostgreSQL, MSSQL and Sybase on Win64... > On second thoughs: I don't have any need to have these components on x64 Windows and have other priorities (e.g. I'd prefer seeing a working dbtestframework on Win64 so Firebird embedded etc can get properly tested), so I think I'll pass on that patch for now.

I still do not understand, why not include (for example new mssqlconnector) with Win64 build?
I do not have Win64 machine so I can not test, but I expect, that there is no problem complile FreeTDS/db-lib for Win64 so if only reason for excluding package from Win64 is "missing client library", then this reason is not valid.
Can anybody explain please why some sql-db connections are presented on Win64 and some not?
Thanks
-Laco.

Reply by email

Sven Barth
to LacaK
LacaK wrote 35 lines
Reinier Olislagers wrote / napísal(a): > On 28-3-2012 12:22, Reinier Olislagers wrote: > >> On 28-3-2012 11:36, Sven Barth wrote: >> >>> Am 28.03.2012 11:12, schrieb Reinier Olislagers: >>> >>>> On 28-3-2012 11:04, Sven Barth wrote: >>>> >>> (b) Maybe nobody needed it yet. I myself might be the first one at all >>> who wanted to interface with Oracle on Windows directly without ODBC. ;) >>> >> <snip> >> >>> Maybe it was only really tested on Linux... >>> >> Mmm... could be... >> >> Thanks Sven, if I get no other answers I think I'll propose a patch that >> builds Oracle, PostgreSQL, MSSQL and Sybase on Win64... >> > > On second thoughs: I don't have any need to have these components on x64 > Windows and have other priorities (e.g. I'd prefer seeing a working > dbtestframework on Win64 so Firebird embedded etc can get properly > tested), so I think I'll pass on that patch for now. > > I still do not understand, why not include (for example new mssqlconnector) with Win64 build? I do not have Win64 machine so I can not test, but I expect, that there is no problem complile FreeTDS/db-lib for Win64 so if only reason for excluding package from Win64 is "missing client library", then this reason is not valid.

I agree here.

Can anybody explain please why some sql-db connections are presented on Win64 and some not?

Perhaps because either nobody verified that they work there or because nobody had expressed enough interest to have them enabled there.

Regards,
Sven

Reply by email