<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Reinier Olislagers wrote / napísal(a):
<blockquote cite="mid:4F740F08.2090506@gmail.com" type="cite">
<pre wrap="">On 28-3-2012 12:22, Reinier Olislagers wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 28-3-2012 11:36, Sven Barth wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Am 28.03.2012 11:12, schrieb Reinier Olislagers:
</pre>
<blockquote type="cite">
<pre wrap="">On 28-3-2012 11:04, Sven Barth wrote:
</pre>
</blockquote>
<pre wrap="">(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. ;)
</pre>
</blockquote>
<pre wrap=""><snip>
</pre>
<blockquote type="cite">
<pre wrap="">Maybe it was only really tested on Linux...
</pre>
</blockquote>
<pre wrap="">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...
</pre>
</blockquote>
<pre wrap=""><!---->
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.
</pre>
</blockquote>
<br>
I still do not understand, why not include (for example new
mssqlconnector) with Win64 build?<br>
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.<br>
Can anybody explain please why some sql-db connections are presented on
Win64 and some not?<br>
Thanks<br>
-Laco.<br>
<br>
</body>
</html>