[PATCH] VMS build update

The attached patch against recent CVS gets the build into shape on
VMS.  Most of the changes are casts to function parameters to make
the compiler stop complaining about type mismatches.  The warnings
are attached in the file vmswarn.txt if anyone is interested.

There were two minor tweaks in vmsbuild.com.  Also, in the
VMS-specific linker options file, I removed the hard-coded path to
Nick's home directory .  In extras/vms.c, I added some code to
lt_dlopen to make it handle a driver name that is an absolute path in
unix syntax (for example when the Driver entry in odbcinst.ini has a
full path rather than the name of an entry in odbc.ini).

After these changes, I built the FreeTDS driver against it and got it
to pass its rather extensive test suite.

Let me know if there are any questions, comments, or concerns about the patch.
--

-- 
________________________________________
Craig A. Berry
mailto:craigberry <at> mac.com

"... getting out of a sonnet is much more
  difficult than getting in."
                  Brad Leithauser

_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> easysoft.com

Re: [PATCH] VMS build update

Craig A. Berry wrote:

> The attached patch against recent CVS gets the build into shape on
> VMS.  Most of the changes are casts to function parameters to make
> the compiler stop complaining about type mismatches.  The warnings
> are attached in the file vmswarn.txt if anyone is interested.
>
> There were two minor tweaks in vmsbuild.com.  Also, in the
> VMS-specific linker options file, I removed the hard-coded path to
> Nick's home directory .  In extras/vms.c, I added some code to
> lt_dlopen to make it handle a driver name that is an absolute path in
> unix syntax (for example when the Driver entry in odbcinst.ini has a
> full path rather than the name of an entry in odbc.ini).
>
> After these changes, I built the FreeTDS driver against it and got it
> to pass its rather extensive test suite.
>
> Let me know if there are any questions, comments, or concerns about 
> the patch.

Cheers, I removed the link to my directory this morning as it happens 

I will add the patch in.

--

-- 
Nick Gorham
Easysoft Limited
http://www.easysoft.com, http://www.unixODBC.org

_______________________________________________

Re: [PATCH] VMS build update

Craig A. Berry wrote:

> The attached patch against recent CVS gets the build into shape on
> VMS.  Most of the changes are casts to function parameters to make
> the compiler stop complaining about type mismatches.  The warnings
> are attached in the file vmswarn.txt if anyone is interested.
>
> There were two minor tweaks in vmsbuild.com.  Also, in the
> VMS-specific linker options file, I removed the hard-coded path to
> Nick's home directory .  In extras/vms.c, I added some code to
> lt_dlopen to make it handle a driver name that is an absolute path in
> unix syntax (for example when the Driver entry in odbcinst.ini has a
> full path rather than the name of an entry in odbc.ini).
>
> After these changes, I built the FreeTDS driver against it and got it
> to pass its rather extensive test suite.
>
Ok, there is a 2.2.13pre with those changes in (not exactly, some have 
been done differently, but I think the net result will be the same) on 
the ftp site now.

I am trying to get to the point of releasing 2.2.13 real soon now, so it 
would help me if folk gave that a try and let me know how it went.

--

-- 
Nick Gorham
Easysoft Limited
http://www.easysoft.com, http://www.unixODBC.org

_______________________________________________

Re: [PATCH] VMS build update

At 2:18 PM +0100 5/20/08, Nick Gorham wrote:
>Craig A. Berry wrote:
>
>The attached patch ....

>Ok, there is a 2.2.13pre with those changes in (not exactly, some have been done differently, but I think
the net result will be the same) on the ftp site now.
>
>I am trying to get to the point of releasing 2.2.13 real soon now, so it would help me if folk gave that a try and
let me know how it went.

Excellent, thanks.  The pre-release snapshot builds with no warnings here and also still looks good with FreeTDS.
--

-- 
________________________________________
Craig A. Berry
mailto:craigberry <at> mac.com

"... getting out of a sonnet is much more
 difficult than getting in."
                 Brad Leithauser
_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> easysoft.com
http://mail.easysoft.com/mailman/listinfo/unixodbc-dev

ODBCGetTryWaitValue support

Hi, ALL,
According to this link: http://msdn.microsoft.com/en-us/library/ms716319(VS.85).aspx
application can set a wait time for connection pooling to wait in order to prevent 
continuous loop.
I just did a search through the unixODBC-2.2.12 sources, and didn't find this function.

Is there a plan of supporting this?

Thank you.

_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> easysoft.com
http://mail.easysoft.com/mailman/listinfo/unixodbc-dev

Re: ODBCGetTryWaitValue support

Igor Korot wrote:

>Hi, ALL,
>According to this link: http://msdn.microsoft.com/en-us/library/ms716319(VS.85).aspx
>application can set a wait time for connection pooling to wait in order to prevent 
>continuous loop.
>I just did a search through the unixODBC-2.2.12 sources, and didn't find this function.
>
>Is there a plan of supporting this?
>
>Thank you.
>
>_______________________________________________
>unixODBC-dev mailing list
>unixODBC-dev <at> easysoft.com
>http://mail.easysoft.com/mailman/listinfo/unixodbc-dev
>
>
>  
>
Well, I will add the entry points to 2.2.13, but in terms of actually 
doing what the MS docs say, it will have to wait untill after 2.2.13.

Feel free to provide a patch.

--

-- 
Nick Gorham
Easysoft Limited
http://www.easysoft.com, http://www.unixODBC.org

Re: ODBCGetTryWaitValue support

Nick,

-----Original Message-----
>From: Nick Gorham <nick.gorham <at> easysoft.com>
>Sent: May 22, 2008 2:04 AM
>To: Igor Korot <ikorot <at> earthlink.net>, Development issues and topics for unixODBC <unixodbc-dev <at> easysoft.com>
>Subject: Re: [unixODBC-dev] ODBCGetTryWaitValue support
>
>Igor Korot wrote:
>
>>Hi, ALL,
>>According to this link: http://msdn.microsoft.com/en-us/library/ms716319(VS.85).aspx
>>application can set a wait time for connection pooling to wait in order to prevent 
>>continuous loop.
>>I just did a search through the unixODBC-2.2.12 sources, and didn't find this function.
>>
>>Is there a plan of supporting this?
>>
>>Thank you.
>>
>>_______________________________________________
>>unixODBC-dev mailing list
>>unixODBC-dev <at> easysoft.com
>>http://mail.easysoft.com/mailman/listinfo/unixodbc-dev
>>
>>
>>  
>>
>Well, I will add the entry points to 2.2.13, but in terms of actually 
>doing what the MS docs say, it will have to wait untill after 2.2.13.

Re: ODBCGetTryWaitValue support

I can account for this in the Qt bits at some point but FYI this does 
not depend upon Qt based code changes from what I can tell.

--
Peter
> I'd love to but I'm afraid I do not know Qt very well. So I'll leave it to
> someone more familiar with qt/unixodbc...
>   

_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> easysoft.com
http://mail.easysoft.com/mailman/listinfo/unixodbc-dev

Re: ODBCGetTryWaitValue support

Peter Harvey wrote:

> I can account for this in the Qt bits at some point but FYI this does 
> not depend upon Qt based code changes from what I can tell.

No, its just in the driver manager. There would be a odbcinst.ini entry

--

-- 
Nick
_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> easysoft.com
http://mail.easysoft.com/mailman/listinfo/unixodbc-dev

SQLDriverConnect question

Hi, ALL,
Does SQLDriverConnect() function support SQL_DRIVER_PROMPT,
SQL_DRIVER_COMPLETE and SQL_DRIVER_COMPLETE_REQUIRED as a
last parameter?

According to http://msdn.microsoft.com/en-us/library/ms715433.aspx

"
SQL_DRIVER_PROMPT: If the connection string does not contain either the DRIVER, DSN, or FILEDSN keyword,
the Driver Manager displays the Data Sources dialog box. It constructs a connection string from the data
source name returned by the dialog box and any other keywords passed to it by the application. If the data
source name returned by the dialog box is empty, the Driver Manager specifies the keyword-value pair
DSN=Default. (This dialog box will not display a data source with the name "Default".)

SQL_DRIVER_COMPLETE or SQL_DRIVER_COMPLETE_REQUIRED: If the connection string specified by the
application includes the DSN keyword, the Driver Manager copies the connection string specified by the
application. Otherwise, it takes the same actions as it does when DriverCompletion is SQL_DRIVER_PROMPT.
"

Thank you.

_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> easysoft.com
http://mail.easysoft.com/mailman/listinfo/unixodbc-dev