libopendbx-devel — Help and discussion about OpenDBX

Re: [opendbx] Mssql connection failed

[Diogenes M. <dio...@gm...>]

Alain,, don't get my wrong.
Im searching for perfomance and good configuration too..

i have severals limitations in english, and that makes me wrong.

thank for share our experience, all learn to these mails.

Saludos

On Thu, May 12, 2011 at 4:55 PM, Alain_Rastoul <al...@fr...> wrote:

> Hi Diogenes,
> You are right about cursors in odbc (client or server cursors), but they
> are
> controlled by the application and here there is no cursor. I had a look at
> the ODBC log trace there was no cursor option positioning either (
> SQLSetStmtAttr ). My server is 2005 SP2+ security fix (9.00.3080.00).
> I'm not a fan of ODBC, but with Windows and MSSQL at least it rocks (avoid
> any ODBC specific syntax commands), on the other side having access to SQL
> Server from Unix is really a plus and I would'nt dismiss FREETDS on the
> contrary - I don't know about ODBC on Linux.
>
> About this test, it is not a "real" test, but repeating the same query will
> make all data and plans in cache on the server side and that's perfect here
> because I want to see connection performance , not sql performance. What I
> suspect here is a connection / deconnection overhead, perhaps I should not
> disconnect between queries in the loop.
> It would be interesting to make a real test - I've thought sometimes about
> a
> tpcc like benchmark - could be interesting in Pharo even Glorp.
>
> Cheers
> Alain
>
>
>
>
>
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> libopendbx-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
> http://www.linuxnetworks.de/doc/index.php/OpenDBX
>

Re: [opendbx] Mssql connection failed

[Mariano M. P. <mar...@gm...>]

On Thu, May 12, 2011 at 10:24 PM, Alain_Rastoul <al...@fr...> wrote:

>  Hi Mariano,
>
> Thanks for the pointers, I'll have a look at those links and tests.
> I think there are lot of developpers using windows and MS technology and
> that it would be nice to document a litle bit more this configuration
> specifically - I remember several posts on squeaks mailing lists about  sql
> server connection with squeak -  prehaps having precompiled binaries would
> help a lot too - Your docs on the build are nice, but not all developpers
> feel comfortable with that boring stuff.
>
>

Hi Alain.  There are binaries. This is explained in:

http://www.squeakdbx.org/Compiling%20and%20installing%20OpenDBX

and it links to:

http://www.linuxnetworks.de/doc/index.php/OpenDBX/Setup/Unix-like

http://www.linuxnetworks.de/doc/index.php/OpenDBX/Setup/Windows

Cheers

Mariano

Regards
> Alain
>
>
> "Mariano Martinez Peck" <mar...@gm...> a écrit dans le message de
> news: BANLkTi=5CM-AXxt=DYb...@ma......
>
>
> On Thu, May 12, 2011 at 1:21 PM, Alain rastoul <Al...@fr...> wrote:
>
>> Hi,
>> I finally got openDbx working with FreeTDS and ODBC, I don't know
>> what went wrong last night, I suppose my computer got tired ;)
>> This is great !
>>
>>
> Well, these are great news!!! :)
> Please, if there is something we can improve in the documentation of the
> website, let us know.
>
>
>
>> However, I found
>> - a much better performance with ODBC backend (DBXOdbcPlatform) in
>> the test I did than with Freetds (DBXMSSQLPlatform) (run the test
>> below, changing DBXOdbcPlatform to DBXMSSQLPlatform).
>> With the ODBC backend the test ran about 2 times faster tha
>
>
>
> Did you see the benchmarks we have ? Check the classes DBXBigBenchmarks,
> DBXTinyBenchmarks and DBXMultipleForksBenchmarks.
> And this link:
> http://www.squeakdbx.org/Benchmarks
>
>
>> nt
>> MSSQL-freetds backend (needs explorations here)
>> - perhaps a problem with TinyInt datatype ?
>>  (not very important)
>>
>
>
> Probably related to:
>
>
> http://www.squeakdbx.org/Mappings%20from%20String%20to%20specific%20squeak%20types%20in%20selects#Whathappenifyouareretrievingarowthathasanotsupportedfield
>
> http://www.linuxnetworks.de/doc/index.php/OpenDBX/DBMS_Datatypes
>
> Cheers
>
>
>> The test below consist read the column definitions of syscolumns and
>> does not need any other database than master.
>> Set myhost, myport, mydb, myuser and mypassword as appropriate.
>> If you uncomment c.xprec, you will have the TinyInt error
>>
>> 500 timesRepeat: [
>>        | conn connectionSettings result  sql |
>>
>>        sql := 'select c.name, c.id,  s.name , c.length --, c.xprec --,
>> c.xscale,  c.xtype
>>        from master..sysobjects as o
>>        inner join master..syscolumns as c
>>         on o.id = c.id
>>        inner join master..systypes as s
>>         on c.xtype = s.xtype
>>        where o.name = ''syscolumns'''.
>>            connectionSettings := DBXConnectionSettings
>>                        host: 'myhost'
>>                        port: '1884'
>>                        database: 'mydb'
>>                        userName: 'myuser'
>>                        userPassword: 'mypassword'.
>>        [       conn := DBXConnection platform: DBXOdbcPlatform new
>> settings:
>> connectionSettings.
>>                conn connect.
>>                conn open.
>>                result := conn execute: sql.
>>                result rowsDo: [ :r |
>>                        1 to: result columnCount do: [:c|
>>                                | v |
>>                                v := r rawValueAt: c.]].
>>        ] ensure: [ conn close ]].
>>
>> Cheers,
>> Alain
>>
>> --
>> Alain_rastoul
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Achieve unprecedented app performance and reliability
>> What every C/C++ and Fortran developer should know.
>> Learn how Intel has extended the reach of its next-generation tools
>> to help boost performance applications - inlcuding clusters.
>> http://p.sf.net/sfu/intel-dev2devmay
>> _______________________________________________
>> libopendbx-devel mailing list
>> lib...@pu...
>>
>> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
>> http://www.linuxnetworks.de/doc/index.php/OpenDBX
>>
>
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
>  ------------------------------
>
>
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
>
> ------------------------------
>
>
>
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> libopendbx-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
> http://www.linuxnetworks.de/doc/index.php/OpenDBX
>
>


-- 
Mariano
http://marianopeck.wordpress.com

Re: [opendbx] Mssql connection failed

[Alain_Rastoul <al...@fr...>]

Hi Mariano,

Thanks for the pointers, I'll have a look at those links and tests.
I think there are lot of developpers using windows and MS technology and that it would be nice to document a litle bit more this configuration specifically - I remember several posts on squeaks mailing lists about  sql server connection with squeak -  prehaps having precompiled binaries would help a lot too - Your docs on the build are nice, but not all developpers feel comfortable with that boring stuff.

Regards
Alain

  "Mariano Martinez Peck" <mar...@gm...> a écrit dans le message de news: BANLkTi=5CM-AXxt=DYb...@ma......



  On Thu, May 12, 2011 at 1:21 PM, Alain rastoul <Al...@fr...> wrote:

    Hi,
    I finally got openDbx working with FreeTDS and ODBC, I don't know
    what went wrong last night, I suppose my computer got tired ;)
    This is great !



  Well, these are great news!!! :)  
  Please, if there is something we can improve in the documentation of the website, let us know. 

   
    However, I found
    - a much better performance with ODBC backend (DBXOdbcPlatform) in
    the test I did than with Freetds (DBXMSSQLPlatform) (run the test
    below, changing DBXOdbcPlatform to DBXMSSQLPlatform).
    With the ODBC backend the test ran about 2 times faster tha


  Did you see the benchmarks we have ? Check the classes DBXBigBenchmarks, DBXTinyBenchmarks and DBXMultipleForksBenchmarks.
  And this link: 
  http://www.squeakdbx.org/Benchmarks
   
    nt
    MSSQL-freetds backend (needs explorations here)
    - perhaps a problem with TinyInt datatype ?
     (not very important)



  Probably related to:

  http://www.squeakdbx.org/Mappings%20from%20String%20to%20specific%20squeak%20types%20in%20selects#Whathappenifyouareretrievingarowthathasanotsupportedfield

  http://www.linuxnetworks.de/doc/index.php/OpenDBX/DBMS_Datatypes 

  Cheers



    The test below consist read the column definitions of syscolumns and
    does not need any other database than master.
    Set myhost, myport, mydb, myuser and mypassword as appropriate.
    If you uncomment c.xprec, you will have the TinyInt error

    500 timesRepeat: [
           | conn connectionSettings result  sql |

           sql := 'select c.name, c.id,  s.name , c.length --, c.xprec --,
    c.xscale,  c.xtype
           from master..sysobjects as o
           inner join master..syscolumns as c
            on o.id = c.id
           inner join master..systypes as s
            on c.xtype = s.xtype
           where o.name = ''syscolumns'''.
               connectionSettings := DBXConnectionSettings
                           host: 'myhost'
                           port: '1884'
                           database: 'mydb'
                           userName: 'myuser'
                           userPassword: 'mypassword'.
           [       conn := DBXConnection platform: DBXOdbcPlatform new settings:
    connectionSettings.
                   conn connect.
                   conn open.
                   result := conn execute: sql.
                   result rowsDo: [ :r |
                           1 to: result columnCount do: [:c|
                                   | v |
                                   v := r rawValueAt: c.]].
           ] ensure: [ conn close ]].

    Cheers,
    Alain

    --
    Alain_rastoul



    ------------------------------------------------------------------------------
    Achieve unprecedented app performance and reliability
    What every C/C++ and Fortran developer should know.
    Learn how Intel has extended the reach of its next-generation tools
    to help boost performance applications - inlcuding clusters.
    http://p.sf.net/sfu/intel-dev2devmay
    _______________________________________________
    libopendbx-devel mailing list
    lib...@li...
    https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
    http://www.linuxnetworks.de/doc/index.php/OpenDBX




  -- 
  Mariano
  http://marianopeck.wordpress.com




------------------------------------------------------------------------------


  ------------------------------------------------------------------------------
  Achieve unprecedented app performance and reliability
  What every C/C++ and Fortran developer should know.
  Learn how Intel has extended the reach of its next-generation tools
  to help boost performance applications - inlcuding clusters.
  http://p.sf.net/sfu/intel-dev2devmay


------------------------------------------------------------------------------

Re: [opendbx] Mssql connection failed

[Alain_Rastoul <al...@fr...>]

Hi Diogenes,
You are right about cursors in odbc (client or server cursors), but they are 
controlled by the application and here there is no cursor. I had a look at 
the ODBC log trace there was no cursor option positioning either ( 
SQLSetStmtAttr ). My server is 2005 SP2+ security fix (9.00.3080.00).
I'm not a fan of ODBC, but with Windows and MSSQL at least it rocks (avoid 
any ODBC specific syntax commands), on the other side having access to SQL 
Server from Unix is really a plus and I would'nt dismiss FREETDS on the 
contrary - I don't know about ODBC on Linux.

About this test, it is not a "real" test, but repeating the same query will 
make all data and plans in cache on the server side and that's perfect here 
because I want to see connection performance , not sql performance. What I 
suspect here is a connection / deconnection overhead, perhaps I should not 
disconnect between queries in the loop.
It would be interesting to make a real test - I've thought sometimes about a 
tpcc like benchmark - could be interesting in Pharo even Glorp.

Cheers
Alain 

Re: [opendbx] Mssql connection failed

[Mariano M. P. <mar...@gm...>]

On Thu, May 12, 2011 at 1:21 PM, Alain rastoul <Al...@fr...> wrote:

> Hi,
> I finally got openDbx working with FreeTDS and ODBC, I don't know
> what went wrong last night, I suppose my computer got tired ;)
> This is great !
>
>
Well, these are great news!!! :)
Please, if there is something we can improve in the documentation of the
website, let us know.



> However, I found
> - a much better performance with ODBC backend (DBXOdbcPlatform) in
> the test I did than with Freetds (DBXMSSQLPlatform) (run the test
> below, changing DBXOdbcPlatform to DBXMSSQLPlatform).
> With the ODBC backend the test ran about 2 times faster tha



Did you see the benchmarks we have ? Check the classes DBXBigBenchmarks,
DBXTinyBenchmarks and DBXMultipleForksBenchmarks.
And this link:
http://www.squeakdbx.org/Benchmarks


> nt
> MSSQL-freetds backend (needs explorations here)
> - perhaps a problem with TinyInt datatype ?
>  (not very important)
>


Probably related to:

http://www.squeakdbx.org/Mappings%20from%20String%20to%20specific%20squeak%20types%20in%20selects#Whathappenifyouareretrievingarowthathasanotsupportedfield

http://www.linuxnetworks.de/doc/index.php/OpenDBX/DBMS_Datatypes

Cheers


> The test below consist read the column definitions of syscolumns and
> does not need any other database than master.
> Set myhost, myport, mydb, myuser and mypassword as appropriate.
> If you uncomment c.xprec, you will have the TinyInt error
>
> 500 timesRepeat: [
>        | conn connectionSettings result  sql |
>
>        sql := 'select c.name, c.id,  s.name , c.length --, c.xprec --,
> c.xscale,  c.xtype
>        from master..sysobjects as o
>        inner join master..syscolumns as c
>         on o.id = c.id
>        inner join master..systypes as s
>         on c.xtype = s.xtype
>        where o.name = ''syscolumns'''.
>            connectionSettings := DBXConnectionSettings
>                        host: 'myhost'
>                        port: '1884'
>                        database: 'mydb'
>                        userName: 'myuser'
>                        userPassword: 'mypassword'.
>        [       conn := DBXConnection platform: DBXOdbcPlatform new
> settings:
> connectionSettings.
>                conn connect.
>                conn open.
>                result := conn execute: sql.
>                result rowsDo: [ :r |
>                        1 to: result columnCount do: [:c|
>                                | v |
>                                v := r rawValueAt: c.]].
>        ] ensure: [ conn close ]].
>
> Cheers,
> Alain
>
> --
> Alain_rastoul
>
>
>
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> libopendbx-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
> http://www.linuxnetworks.de/doc/index.php/OpenDBX
>



-- 
Mariano
http://marianopeck.wordpress.com

Re: [opendbx] Mssql connection failed

[<dio...@gm...>]

Hi alain..

If i remeber well obdc work with a cache and open a cursor to obtein the resultser. You can check this with the trace tools of mssql server. A good test may be select with diferent queries, inserts, deletes,updates, etc.. Not repeating the same query. Please would you send to as you SO and mssql version.. May be i was wrong and odbc is faster than freetds, with the right configuration. 


Best
D.
Enviado desde mi BlackBerry® de Claro Argentina

-----Original Message-----
From: Alain rastoul <Al...@fr...>
Date: Thu, 12 May 2011 13:21:23 
To: <lib...@li...>
Reply-To: OpenDBX devel list <lib...@li...>
Subject: Re: [opendbx] Mssql connection failed

Hi,
I finally got openDbx working with FreeTDS and ODBC, I don't know 
what went wrong last night, I suppose my computer got tired ;)
This is great !

However, I found
- a much better performance with ODBC backend (DBXOdbcPlatform) in 
the test I did than with Freetds (DBXMSSQLPlatform) (run the test 
below, changing DBXOdbcPlatform to DBXMSSQLPlatform).
With the ODBC backend the test ran about 2 times faster thant 
MSSQL-freetds backend (needs explorations here)
- perhaps a problem with TinyInt datatype ?
 (not very important) 

The test below consist read the column definitions of syscolumns and 
does not need any other database than master.
Set myhost, myport, mydb, myuser and mypassword as appropriate.
If you uncomment c.xprec, you will have the TinyInt error

500 timesRepeat: [
	| conn connectionSettings result  sql |

	sql := 'select c.name, c.id,  s.name , c.length --, c.xprec --, 
c.xscale,  c.xtype 
	from master..sysobjects as o
	inner join master..syscolumns as c
	 on o.id = c.id
	inner join master..systypes as s 
	 on c.xtype = s.xtype
	where o.name = ''syscolumns'''.
	    connectionSettings := DBXConnectionSettings
	                host: 'myhost'
	                port: '1884'
	                database: 'mydb'
	                userName: 'myuser'
	                userPassword: 'mypassword'.
	[	conn := DBXConnection platform: DBXOdbcPlatform new settings: 
connectionSettings.
		conn connect.
		conn open.
		result := conn execute: sql.
		result rowsDo: [ :r | 
			1 to: result columnCount do: [:c|
				| v |
				v := r rawValueAt: c.]].
	] ensure: [ conn close ]].
	
Cheers,
Alain

-- 
Alain_rastoul


------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
libopendbx-devel mailing list
lib...@li...
https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
http://www.linuxnetworks.de/doc/index.php/OpenDBX

Re: [opendbx] Mssql connection failed

[Alain r. <Al...@fr...>]

Hi,
I finally got openDbx working with FreeTDS and ODBC, I don't know 
what went wrong last night, I suppose my computer got tired ;)
This is great !

However, I found
- a much better performance with ODBC backend (DBXOdbcPlatform) in 
the test I did than with Freetds (DBXMSSQLPlatform) (run the test 
below, changing DBXOdbcPlatform to DBXMSSQLPlatform).
With the ODBC backend the test ran about 2 times faster thant 
MSSQL-freetds backend (needs explorations here)
- perhaps a problem with TinyInt datatype ?
 (not very important) 

The test below consist read the column definitions of syscolumns and 
does not need any other database than master.
Set myhost, myport, mydb, myuser and mypassword as appropriate.
If you uncomment c.xprec, you will have the TinyInt error

500 timesRepeat: [
	| conn connectionSettings result  sql |

	sql := 'select c.name, c.id,  s.name , c.length --, c.xprec --, 
c.xscale,  c.xtype 
	from master..sysobjects as o
	inner join master..syscolumns as c
	 on o.id = c.id
	inner join master..systypes as s 
	 on c.xtype = s.xtype
	where o.name = ''syscolumns'''.
	    connectionSettings := DBXConnectionSettings
	                host: 'myhost'
	                port: '1884'
	                database: 'mydb'
	                userName: 'myuser'
	                userPassword: 'mypassword'.
	[	conn := DBXConnection platform: DBXOdbcPlatform new settings: 
connectionSettings.
		conn connect.
		conn open.
		result := conn execute: sql.
		result rowsDo: [ :r | 
			1 to: result columnCount do: [:c|
				| v |
				v := r rawValueAt: c.]].
	] ensure: [ conn close ]].
	
Cheers,
Alain

-- 
Alain_rastoul

Re: [opendbx] [SqueakDBX] OpenDBX: Another command is already in progress

[Norbert S. <no...@li...>]

Hi Mariano

> Thanks Norbert. Just to be sure you understood me. I KNOW that SqueakDBX
> must call odbx_result until I get ODBX_RES_DONE.
> My question was if you recognize the error of postgres I've sent you, as the
> cause of not doing exactly that ;)
> I mean, if you know if that error of posgresql is becuase of that or
> something not related.

Jep, this error should be exactly the result of not calling odbx_result 
until its done :-)


Norbert

Re: [opendbx] [SqueakDBX] OpenDBX: Another command is already in progress

[Mariano M. P. <mar...@gm...>]

On Wed, May 11, 2011 at 10:15 AM, Norbert Sendetzky <
no...@li...> wrote:

> Hi Mariano
>
> > Hi Norbert.  John is having a problem with SqueakDBX and I just want to
> be
> > sure it is what I think.... He gets the error "Another command is already
> in
> > progress" and acoording to pgsql documentation  "PQgetResult must be
> called
> > repeatedly until it returns a null pointer,  *indicating* that the
> *command*
> >   *is* done."
> >
> > So...in the OpenDBX world, this would mean that he (SqueakDBX) didn't
> call
> >
> > int odbx_result( odbx_t* handle, odbx_result_t** result, struct timeval*
> > timeout, unsigned long chunk )
> >
> > up to receive NULL ??
>
> Yes, odbx_result() must be called until it returns ODBX_RES_DONE.
>

Thanks Norbert. Just to be sure you understood me. I KNOW that SqueakDBX
must call odbx_result until I get ODBX_RES_DONE.
My question was if you recognize the error of postgres I've sent you, as the
cause of not doing exactly that ;)
I mean, if you know if that error of posgresql is becuase of that or
something not related.

thanks in advance!

Mariano


>
>
> Norbert
>
>
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> libopendbx-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
> http://www.linuxnetworks.de/doc/index.php/OpenDBX
>



-- 
Mariano
http://marianopeck.wordpress.com

Re: [opendbx] Mssql connection failed

[Norbert S. <no...@li...>]

Hi Diogenes, Alain
 >> just found it:
 >> 
http://www.linuxnetworks.de/doc/index.php/OpenDBX/Setup/Windows/Building_with_MinGW
 >> see comment on MSSQL Server backend
 >> "The mssql backend is primarily intended for Unix environments where a
 >> native client library is not available for the MS SQL Server and FreeTDS
 >> library provides the only alternative. On Windows platforms, the native
 >> client is an ODBC driver so it's better to use the odbc backend."
 >> to be honest, it seems reasonable, ODBC is not bad and the driver in 
sync
 >
> In addition Glorp dont have a ODBCPlatform.. if you chose that
> platform you must extend the DatabasePlatform. In fact the right model
> , may be  a superclass for ODBC and specifics classes for each DBMS.

The statement regarding ODBC is for using the OpenDBX ODBC backend 
(opendbx-odbc package). An application using OpenDBX won't notice this 
fact besides the ODBC SQL Syntax might be slightly different in some cases.


Norbert

Re: [opendbx] [SqueakDBX] OpenDBX: Another command is already in progress

[Norbert S. <no...@li...>]

Hi Mariano

> Hi Norbert.  John is having a problem with SqueakDBX and I just want to be
> sure it is what I think.... He gets the error "Another command is already in
> progress" and acoording to pgsql documentation  "PQgetResult must be called
> repeatedly until it returns a null pointer,  *indicating* that the *command*
>   *is* done."
>
> So...in the OpenDBX world, this would mean that he (SqueakDBX) didn't call
>
> int odbx_result( odbx_t* handle, odbx_result_t** result, struct timeval*
> timeout, unsigned long chunk )
>
> up to receive NULL ??

Yes, odbx_result() must be called until it returns ODBX_RES_DONE.


Norbert

Re: [opendbx] Mssql connection failed

[Alain r. <Al...@fr...>]

I'm willing to be conviced by freetds.
:)
Cheers

-- 
Alain_rastoul

Re: [opendbx] [SqueakDBX] OpenDBX: Another command is already in progress

[Mariano M. P. <mar...@gm...>]

Hi Norbert.  John is having a problem with SqueakDBX and I just want to be
sure it is what I think.... He gets the error "Another command is already in
progress" and acoording to pgsql documentation  "PQgetResult must be called
repeatedly until it returns a null pointer,  *indicating* that the *command*
 *is* done."

So...in the OpenDBX world, this would mean that he (SqueakDBX) didn't call

int odbx_result( odbx_t* handle, odbx_result_t** result, struct timeval*
timeout, unsigned long chunk )

up to receive NULL ??


or this has nothing to do and it is another error??

thanks

mariano

---------- Forwarded message ----------
From: John Toohey <jt...@pa...>
Date: Tue, May 10, 2011 at 4:31 PM
Subject: [SqueakDBX] OpenDBX: Another command is already in progress
To: squeakdbx <squ...@li...>


I get this error a lot when my system is under load. According to the pgsql
docs, I should do this, "PQgetResult must be called repeatedly until it
returns a null pointer,
*indicating* that the *command* *is* done."

How do I handle this type of error in GlorpDBX? I'm using Pharo 1.2 and the
Glorp/DBX build that was available when that was released.

-- 
~JT



_______________________________________________
SqueakDBX mailing list
Squ...@li...
http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx




-- 
Mariano
http://marianopeck.wordpress.com

Re: [opendbx] Mssql connection failed

[Diogenes M. <dio...@gm...>]

well. I don't knew thats comments... but i did benchmarks and free tds
works better..
In fact i have 3 system in production and freetds work better.. and
without tipical ADO distributions problems..
You are free to chose which platform to use. :)

besides, When you use ODBC, you must use, ODBC Syntax.. that is little
bit diferent than ANSI, loosing portability

based on that i can say, "Free tds platfom is the better option".

In addition Glorp dont have a ODBCPlatform.. if you chose that
platform you must extend the DatabasePlatform. In fact the right model
, may be  a superclass for ODBC and specifics classes for each DBMS.

Best..

On Tue, May 10, 2011 at 2:04 PM, Alain_Rastoul <al...@fr...> wrote:
> just found it:
> http://www.linuxnetworks.de/doc/index.php/OpenDBX/Setup/Windows/Building_with_MinGW
> see comment on MSSQL Server backend
> "The mssql backend is primarily intended for Unix environments where a
> native client library is not available for the MS SQL Server and FreeTDS
> library provides the only alternative. On Windows platforms, the native
> client is an ODBC driver so it's better to use the odbc backend."
> to be honest, it seems reasonable, ODBC is not bad and the driver in sync
>
> "Alain_Rastoul" <al...@fr...> a écrit dans le
> message de news: iqbqj0$hpg$1...@do......
>> Thanks Mariano and Diogenes for your answers.
>> I can't check your suggestions (env.variables, though I'm quite sure I
>> did, and blob fields) this evening but tomorrow .
>> As I said, I was able to connect with the tsql.exe utility compiled with
>> freetds using sockets, my server has the 2 authentications modes (sql and
>> nt) and is listening on sockets, so I would say freetds seems to be ok.
>> I downloaded the opendbx win 32 binaries from the link on the squeakdbx
>> site and I'm sure I've seen a comment saying that the "prefered backend
>> was odbc" because of native drivers (on this site I think) - but I could
>> not find the link anymore.
>> I'll send it to you when I find it.
>> Thanks again
>> cheers
>> Alain
>>
>>
>> "Alain rastoul" <Al...@fr...> a écrit dans le
>> message de news:
>> alm...@Ne......
>> I dowloaded opendbx binaries and freetds sources, mingw, msys and
>> built freetds. I installed opendbx in my pharo1.3 with the gofer
>> script found in docs.
>> Connection to my sql server with the freetds tsql utility was ok, but
>> from pharo I always got «connection failed» then a crash (pharo
>> process exit).
>> I saw in opendbx docs that from a windows client odbc backend is
>> prefered, changed backend of DBXMSSQLPlatform to 'odbc' then
>> connection to my server with a system dsn was ok, but I have «unknow
>> problem with executeStatement» when I execute a «select * from
>> mytable»
>> Is there a better way to proceed with opendbx-mssql?
>> Can I connect without a dsn ?
>>
>> Any advice or comments are welcome.
>>
>> TIA
>> Cheers
>>
>> --
>> Alain_rastoul
>>
>>
>> ------------------------------------------------------------------------------
>> Achieve unprecedented app performance and reliability
>> What every C/C++ and Fortran developer should know.
>> Learn how Intel has extended the reach of its next-generation tools
>> to help boost performance applications - inlcuding clusters.
>> http://p.sf.net/sfu/intel-dev2devmay
>>
>>
>>
>>
>
>
> --------------------------------------------------------------------------------
>
>
>> ------------------------------------------------------------------------------
>> Achieve unprecedented app performance and reliability
>> What every C/C++ and Fortran developer should know.
>> Learn how Intel has extended the reach of its next-generation tools
>> to help boost performance applications - inlcuding clusters.
>> http://p.sf.net/sfu/intel-dev2devmay
>
>
> --------------------------------------------------------------------------------
>
>
>>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> libopendbx-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
> http://www.linuxnetworks.de/doc/index.php/OpenDBX
>
>

Re: [opendbx] Mssql connection failed

[Alain_Rastoul <al...@fr...>]

just found it:
http://www.linuxnetworks.de/doc/index.php/OpenDBX/Setup/Windows/Building_with_MinGW
see comment on MSSQL Server backend
"The mssql backend is primarily intended for Unix environments where a 
native client library is not available for the MS SQL Server and FreeTDS 
library provides the only alternative. On Windows platforms, the native 
client is an ODBC driver so it's better to use the odbc backend."
to be honest, it seems reasonable, ODBC is not bad and the driver in sync

"Alain_Rastoul" <al...@fr...> a écrit dans le 
message de news: iqbqj0$hpg$1...@do......
> Thanks Mariano and Diogenes for your answers.
> I can't check your suggestions (env.variables, though I'm quite sure I 
> did, and blob fields) this evening but tomorrow .
> As I said, I was able to connect with the tsql.exe utility compiled with 
> freetds using sockets, my server has the 2 authentications modes (sql and 
> nt) and is listening on sockets, so I would say freetds seems to be ok.
> I downloaded the opendbx win 32 binaries from the link on the squeakdbx 
> site and I'm sure I've seen a comment saying that the "prefered backend 
> was odbc" because of native drivers (on this site I think) - but I could 
> not find the link anymore.
> I'll send it to you when I find it.
> Thanks again
> cheers
> Alain
>
>
> "Alain rastoul" <Al...@fr...> a écrit dans le 
> message de news: 
> alm...@Ne......
> I dowloaded opendbx binaries and freetds sources, mingw, msys and
> built freetds. I installed opendbx in my pharo1.3 with the gofer
> script found in docs.
> Connection to my sql server with the freetds tsql utility was ok, but
> from pharo I always got «connection failed» then a crash (pharo
> process exit).
> I saw in opendbx docs that from a windows client odbc backend is
> prefered, changed backend of DBXMSSQLPlatform to 'odbc' then
> connection to my server with a system dsn was ok, but I have «unknow
> problem with executeStatement» when I execute a «select * from
> mytable»
> Is there a better way to proceed with opendbx-mssql?
> Can I connect without a dsn ?
>
> Any advice or comments are welcome.
>
> TIA
> Cheers
>
> -- 
> Alain_rastoul
>
>
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
>
>
>
>


--------------------------------------------------------------------------------


> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay


--------------------------------------------------------------------------------


> 

Re: [opendbx] Mssql connection failed

[Alain_Rastoul <al...@fr...>]

Thanks Mariano and Diogenes for your answers.
I can't check your suggestions (env.variables, though I'm quite sure I did, 
and blob fields) this evening but tomorrow .
As I said, I was able to connect with the tsql.exe utility compiled with 
freetds using sockets, my server has the 2 authentications modes (sql and 
nt) and is listening on sockets, so I would say freetds seems to be ok.
I downloaded the opendbx win 32 binaries from the link on the squeakdbx site 
and I'm sure I've seen a comment saying that the "prefered backend was odbc" 
because of native drivers (on this site I think) - but I could not find the 
link anymore.
I'll send it to you when I find it.
Thanks again
cheers
Alain


"Alain rastoul" <Al...@fr...> a écrit dans le 
message de news: alm...@Ne......
I dowloaded opendbx binaries and freetds sources, mingw, msys and
built freetds. I installed opendbx in my pharo1.3 with the gofer
script found in docs.
Connection to my sql server with the freetds tsql utility was ok, but
from pharo I always got «connection failed» then a crash (pharo
process exit).
I saw in opendbx docs that from a windows client odbc backend is
prefered, changed backend of DBXMSSQLPlatform to 'odbc' then
connection to my server with a system dsn was ok, but I have «unknow
problem with executeStatement» when I execute a «select * from
mytable»
Is there a better way to proceed with opendbx-mssql?
Can I connect without a dsn ?

Any advice or comments are welcome.

TIA
Cheers

-- 
Alain_rastoul


------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay 

Re: [opendbx] Mssql connection failed

[<dio...@gm...>]

Hi...

Well the better way to connect to MSSql from pharo is with  freetds platform.
Not via ODBC.

You need check a couple things:

1: all dll's are on the path.
2: freetds.conf is on.
3: the sql server accept tcp conexion, not name pipes or shared memory.
4: the enviroments variables are right configurates
5: check the server accept dual mode authentication
6: you can enable the debug mode, for your tds connection from freedts.conf , for more information and register activity in a log file.

For more detail, you can check http://www.squeakdbx.org in the documentation section. The configuration section for freetds for linux apply for windows too.

Best

D.

Pd: pharo 1.3 is unstable yet. The dbx team (previously squeakdbx) are working in a refactoring and uptade over 1.3 but this version we are working yet.
Pd2: if you wanna more customized support(check conexion string, check a MNU etc.), can  sendme an email a private email.
Pd3: this version of squeak dbx dont support Blob data types (like Blob, image, Clob, Text, etc). I guess those data types, will be supportes in nexts versions.

Enviado desde mi BlackBerry® de Claro Argentina

-----Original Message-----
From: Alain rastoul <Al...@fr...>
Date: Tue, 10 May 2011 14:00:21 
To: <lib...@li...>
Reply-To: OpenDBX devel list <lib...@li...>
Subject: [opendbx] Mssql connection failed

I dowloaded opendbx binaries and freetds sources, mingw, msys and 
built freetds. I installed opendbx in my pharo1.3 with the gofer 
script found in docs.
Connection to my sql server with the freetds tsql utility was ok, but 
from pharo I always got «connection failed» then a crash (pharo 
process exit).
I saw in opendbx docs that from a windows client odbc backend is 
prefered, changed backend of DBXMSSQLPlatform to 'odbc' then 
connection to my server with a system dsn was ok, but I have «unknow 
problem with executeStatement» when I execute a «select * from 
mytable»
Is there a better way to proceed with opendbx-mssql?
Can I connect without a dsn ?

Any advice or comments are welcome.

TIA
Cheers

-- 
Alain_rastoul


------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
libopendbx-devel mailing list
lib...@li...
https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
http://www.linuxnetworks.de/doc/index.php/OpenDBX

Re: [opendbx] Mssql connection failed

[Mariano M. P. <mar...@gm...>]

Hi alain. I cc'ed also the SqueakDBX mailing list since there were a couple
of guys using SqueakDBX with MSSQL.

Miguel and Diogenes can help you.

On Tue, May 10, 2011 at 2:00 PM, Alain rastoul <Al...@fr...> wrote:

> I dowloaded opendbx binaries and freetds sources, mingw, msys and
> built freetds. I installed opendbx in my pharo1.3 with the gofer
> script found in docs.
> Connection to my sql server with the freetds tsql utility was ok, but
> from pharo I always got «connection failed» then a crash (pharo
> process exit).
>

Did you see the dump file to see if there is some info?


> I saw in opendbx docs that from a windows client odbc backend is
> prefered, changed backend of DBXMSSQLPlatform


so the error described is with DBXMSSQLPlatform?  but with DBXOdbcBackend
you could connect ?


> to 'odbc' then
> connection to my server with a system dsn was ok, but I have «unknow
> problem with executeStatement» when I execute a «select * from
> mytable»
>

wierd...I never seen this.  Do you know who is throwing such an error ?

Is there a better way to proceed with opendbx-mssql?
> Can I connect without a dsn ?
>

I don't know. I always used SDN.


>
> Any advice or comments are welcome.
>
> TIA
> Cheers
>
> --
> Alain_rastoul
>
>
>
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> libopendbx-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
> http://www.linuxnetworks.de/doc/index.php/OpenDBX
>



-- 
Mariano
http://marianopeck.wordpress.com

[opendbx] Mssql connection failed

[Alain r. <Al...@fr...>]

I dowloaded opendbx binaries and freetds sources, mingw, msys and 
built freetds. I installed opendbx in my pharo1.3 with the gofer 
script found in docs.
Connection to my sql server with the freetds tsql utility was ok, but 
from pharo I always got «connection failed» then a crash (pharo 
process exit).
I saw in opendbx docs that from a windows client odbc backend is 
prefered, changed backend of DBXMSSQLPlatform to 'odbc' then 
connection to my server with a system dsn was ok, but I have «unknow 
problem with executeStatement» when I execute a «select * from 
mytable»
Is there a better way to proceed with opendbx-mssql?
Can I connect without a dsn ?

Any advice or comments are welcome.

TIA
Cheers

-- 
Alain_rastoul

Re: [opendbx] OpenDBX with PowerDNS and FreeTDS - Error: Attempt to initiate a new Adaptive Server operation with results pending

[Norbert S. <no...@li...>]

Hi all

> I get the errors below after a while (About 20mins) with PowerDNS on an
> OpenDBX+FreeTDS backend:
>
> Mar 31 13:33:20 ns01 pdns[3921]: Database module reported condition
> which prevented lookup (Error: DB statement failed) sending out servfail
>
> Mar 31 13:33:20 ns01 pdns[3921]: [OpendbxBackend] execStmt: Unable to
> execute query - Attempt to initiate a new Adaptive Server operation with
> results pending, Success
>
> Once a backend thread starts giving this error it does not respond to
> any more queries. The MSSQL server shows no unusual queries before a
> thread locks up with this error.
>
> Information I have found so far suggest it is an application issue and
> either OpenDBX or the PowerDNS OpenDBX backend because it is not calling
> dbresults in certain situations:
>
> As for "Attempt to initiate a new Adaptive Server operation with results
> pending", that's a logical error on the part of the application: you
> have
> to read your results or cancel them before issuing a new query.  Cf. FAQ
> http://www.freetds.org/faq.html#pending.
>
> "Once dbsqlexec returns SUCCEED, the application must call dbresults to
> process the results."
>
> Can anyone help with a fix or patch?

As I said in another mail, I don't think it possible to fix this, 
because I think it is a threading issue and the underlying dblib is not 
thread safe.

Your only working options to interface a MS SQL server using PowerDNS 
are either using the OpenDBX sybase or odbc backend.


Norbert

[opendbx] OpenDBX with PowerDNS and FreeTDS - Error: Attempt to initiate a new Adaptive Server operation with results pending

[Robert D. <Ro...@sa...>]

Hi Everyone,

 

 

I get the errors below after a while (About 20mins) with PowerDNS on an
OpenDBX+FreeTDS backend:

Mar 31 13:33:20 ns01 pdns[3921]: Database module reported condition
which prevented lookup (Error: DB statement failed) sending out servfail

Mar 31 13:33:20 ns01 pdns[3921]: [OpendbxBackend] execStmt: Unable to
execute query - Attempt to initiate a new Adaptive Server operation with
results pending, Success

 

Once a backend thread starts giving this error it does not respond to
any more queries. The MSSQL server shows no unusual queries before a
thread locks up with this error.

 

Information I have found so far suggest it is an application issue and
either OpenDBX or the PowerDNS OpenDBX backend because it is not calling
dbresults in certain situations:

As for "Attempt to initiate a new Adaptive Server operation with results
pending", that's a logical error on the part of the application: you
have
to read your results or cancel them before issuing a new query.  Cf. FAQ
http://www.freetds.org/faq.html#pending.  

 

"Once dbsqlexec returns SUCCEED, the application must call dbresults to
process the results."

 

Can anyone help with a fix or patch?

 

 

 

Thanks,

 

 

Rob


The SAQ Group

Registered Office: 18 Chapel Street, Petersfield, Hampshire GU32 3DZ
SAQ is the trading name of SEMTEC Limited. Registered in England & Wales
Company Number: 06481952

http://www.saqnet.co.uk AS29219

SAQ Group Delivers high quality, honestly priced communication and I.T. services to UK Business.

Broadband : Domains : Email : Hosting : CoLo : Servers : Racks : Transit : Backups : Managed Networks : Remote Support.

ISPA Member

Re: [opendbx] Building errors opendbx 1.4.5

[Mariano M. P. <mar...@gm...>]

On Mon, Mar 21, 2011 at 12:27 PM, Miguel Sanchez <mik...@gm...>wrote:

> Hi Mariano,
>
> On Norberts suggestion I'm cutting over to try with the DBXObcPlatform
> but I'm still getting a fatal error on odbx_bind.
>
> I was wondering, if I'm using DBXOdbcPlatform won't I need to give it
> a DSN rather than a host name?


yes.

Checl #createConnection  for DBXMsSQLFacility or DBXOdbcMSSQLFacility or
DBXOdbcPostgreFacility


>  Are there any special instructions for
> configuring DBXConnectionSettings on an ODBC connection?
>

No, just using the TDS name in "host". Check those #createConnection as
example.


>
> Regards,
>
>
> Miguel
>
> On 18 March 2011 21:55, Mariano Martinez Peck <mar...@gm...>
> wrote:
> > Hi Miguel, what happens if you try with 1.5.0 ??
> >
> > As far as I can see in 1.4.5, odbxlib.c    at the end there is a big if:
> >
> > #ifdef HAVE_WINDOWS_H
> > #include <windows.h>
> > #endif
> >
> >
> > static int _odbx_lib_register( struct odbx_t* handle, const char* library
> )
> >
> > -......
> >
> >
> > #else
> > #error "Building shared libraries requires capabilities to load libraries
> > dynamically"
> > #endif
> >
> >
> > I have no idea.....Norbert will probably help you.
> >
> > Cheers
> >
> > Mariano
> >
> >
> >
> > On Fri, Mar 18, 2011 at 12:10 PM, Miguel Sanchez <
> mik...@gm...>
> > wrote:
> >>
> >> Hi All,
> >>
> >> I'm trying to make opendbx-1.4.5 under MingW on Win XP SP3. I get the
> >> following error on make .
> >> (Despite this error I can see it has built
> >> ./backends/mssql/.libs/libmssqlbackend-1.dll). I presume what is not
> >> being built is libopendbx?
> >> .
> >> .
> >> .
> >> libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I..
> >> -DLIBVERSION=10405 -D
> >> LOCALEDIR=\"/usr/local/share/locale\"
> -DLIBPATH=\"/usr/local/lib/opendbx\"
> >> -DLIB
> >> PREFIX=\"lib\" -DLIBSUFFIX=\"-1.dll\" -Ic:/mingw/msys/1.0/local/include
> -g
> >> -O2 -
> >> MT libopendbx_la-odbxlib.lo -MD -MP -MF .deps/libopendbx_la-odbxlib.Tpo
> -c
> >> odbxl
> >> ib.c  -DDLL_EXPORT -DPIC -o .libs/libopendbx_la-odbxlib.o
> >> odbxlib.c:259:2: error: #error "Building shared libraries requires
> >> capabilities
> >> to load libraries dynamically"
> >> make[2]: *** [libopendbx_la-odbxlib.lo] Error 1
> >> make[2]: Leaving directory `/opendbx/lib'
> >> make[1]: *** [all-recursive] Error 1
> >> make[1]: Leaving directory `/opendbx'
> >> make: *** [all] Error 2
> >>
> >> My configuration  was as follows.
> >>
> >> $ CPPFLAGS="-Ic:/mingw/msys/1.0/local/include"
> >> LDFLAGS="-Lc:/mingw/msys/1.0/loc
> >> al/lib" configure --disable-utils --with-backends="mssql"
> >>
> >>
> >> Best Regards,
> >>
> >>
> >> Miguel
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> Colocation vs. Managed Hosting
> >> A question and answer guide to determining the best fit
> >> for your organization - today and in the future.
> >> http://p.sf.net/sfu/internap-sfd2d
> >> _______________________________________________
> >> libopendbx-devel mailing list
> >> lib...@li...
> >> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
> >> http://www.linuxnetworks.de/doc/index.php/OpenDBX
> >
> >
> >
> ------------------------------------------------------------------------------
> > Colocation vs. Managed Hosting
> > A question and answer guide to determining the best fit
> > for your organization - today and in the future.
> > http://p.sf.net/sfu/internap-sfd2d
> > _______________________________________________
> > libopendbx-devel mailing list
> > lib...@li...
> > https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
> > http://www.linuxnetworks.de/doc/index.php/OpenDBX
> >
> >
>
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> libopendbx-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
> http://www.linuxnetworks.de/doc/index.php/OpenDBX
>

Re: [opendbx] Building errors opendbx 1.4.5

[Norbert S. <no...@li...>]

Hi Miguel

> I have to admit I couldn't work out why I would need to compile
> freeTDS on Windows when there are native libraries that MS provides.
> Having said that I built freeTDS and tested the utilities (tsql)
> successfully on my dev DB.

FreeTDS is mostly useful for Unix-like systems but for Windows 
platforms, ODBC should be preferred.

> I've included my config.log (zipped in config.log.gz).

The output is strange because the WIN32 platform is recognized according 
to your config.log. Your config.h generated after the configure run 
should also contain a

#define WIN32 1


Norbert

Re: [opendbx] Building errors opendbx 1.4.5

[Norbert S. <no...@li...>]

Hi Miguel

> On Norberts suggestion I'm cutting over to try with the DBXObcPlatform
> but I'm still getting a fatal error on odbx_bind.
>
> I was wondering, if I'm using DBXOdbcPlatform won't I need to give it
> a DSN rather than a host name?  Are there any special instructions for
> configuring DBXConnectionSettings on an ODBC connection?

I think there is some misunderstanding. OpenDBX provides an ODBC backend 
itself and this is the preferred way on Windows platforms to connect to 
MS SQL Server. You need to run configure using

configure --disable-utils --with-backends="odbc"

But that won't solve your problem. That's why I asked you for the 
config.log, so I can see what went wrong.


Norbert

Re: [opendbx] Building errors opendbx 1.4.5

[Miguel S. <mik...@gm...>]

Hi Norbert,


Firstly thanks for you quick response.

I'll try compiling  the ODBC backend.

I have to admit I couldn't work out why I would need to compile
freeTDS on Windows when there are native libraries that MS provides.
Having said that I built freeTDS and tested the utilities (tsql)
successfully on my dev DB.

I've included my config.log (zipped in config.log.gz).

I was looking for native libraries because I was under the impression
that ODBC was far more inefficient.......


Many thanks,


Miguel
On 18 March 2011 22:09, Norbert Sendetzky <no...@li...> wrote:
> Hi Miguel
>
>> I'm trying to make opendbx-1.4.5 under MingW on Win XP SP3. I get the
>> following error on make .
>> (Despite this error I can see it has built
>> ./backends/mssql/.libs/libmssqlbackend-1.dll). I presume what is not
>> being built is libopendbx?
>> .
>> odbxlib.c:259:2: error: #error "Building shared libraries requires capabilities
>> to load libraries dynamically"
>
> This is a little bit strange as it means that the WIN32 platform isn't
> recognized. Could you please send me your config.log file?
>
>> My configuration  was as follows.
>>
>> $ CPPFLAGS="-Ic:/mingw/msys/1.0/local/include" LDFLAGS="-Lc:/mingw/msys/1.0/loc
>> al/lib" configure --disable-utils --with-backends="mssql"
>
> Besides from this error I would recommend you to use the ODBC backend on
> Win32 platforms as this is the native method supported by MS SQL Server.
> The "mssql" backend is mainly for Unix-like systems that have to use
> FreeTDS.
>
>
> Norbert
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> libopendbx-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
> http://www.linuxnetworks.de/doc/index.php/OpenDBX
>