Stergios Zissakis | 1 Jul 08:52 2004
Picon
Picon

Re: ODBC Developers

Hi there,

I can tackle 1 and 2. They will also serve as a good introduction to both
ODBC, the driver and unicode.
Where can I get details/specs for all these?

Also another thing that I have come across when using psqlODBC with OTL
(http://otl.sourceforge.net/home.htm) is that the driver
will not work when inserting data with a buffer size other than 1 (this is
the size of the otl_stream buffer).

Regards,
Sterge

-----Original Message-----
From: pgsql-odbc-owner <at> postgresql.org
[mailto:pgsql-odbc-owner <at> postgresql.org]On Behalf Of Dave Page
Sent: Wednesday, June 30, 2004 12:45 PM
To: pgsql-odbc <at> postgresql.org
Subject: [ODBC] ODBC Developers

Hi All,

As many of you will know, I recently placed a news item on
www.postgresql.org to try to get some new developers working on
psqlODBC. I was pleseantly surprised to find that after just a few days
I had received eight responses from people interested in joining the
project. This message has been BCC'd to them.

First of all, I'd like to say thank you to those that responded - input
(Continue reading)

Dave Page | 1 Jul 09:52 2004
Picon

Re: ODBC Developers


> -----Original Message-----
> From: Stergios Zissakis [mailto:szis <at> intranet.gr] 
> Sent: 01 July 2004 07:52
> To: Dave Page; pgsql-odbc <at> postgresql.org
> Subject: RE: [ODBC] ODBC Developers
> 
> Hi there,

Hi,

> I can tackle 1 and 2. They will also serve as a good 
> introduction to both ODBC, the driver and unicode.
> Where can I get details/specs for all these?

Excellent :-). ODBC is a Microsoft thing, so they have the definitive
reference. It's part of the MDAC SDK -
http://www.microsoft.com/downloads/details.aspx?familyid=5067faf8-0db4-4
29a-b502-de4329c8c850&languageid=f49e8428-7071-4979-8a67-3cffcb0c2524&di
splaylang=en

There used to be some validation and test tools included which may be of
use.

> Also another thing that I have come across when using 
> psqlODBC with OTL
> (http://otl.sourceforge.net/home.htm) is that the driver will 
> not work when inserting data with a buffer size other than 1 
> (this is the size of the otl_stream buffer).

(Continue reading)

Dave Page | 1 Jul 09:22 2004
Picon

Re: ODBC Developers


> -----Original Message-----
> From: Peter Eisentraut [mailto:peter_e <at> gmx.net] 
> Sent: 30 June 2004 18:11
> To: Dave Page; pgsql-odbc <at> postgresql.org
> Subject: Re: [ODBC] ODBC Developers
> 
> Dave Page wrote:
> > 3) An audit of the code for possible buffer overrun 
> problems should be 
> > undertaken.
> 
> I'm planning to rip out all uses of the libc string functions 
> and replace them by pqexpbuffer that is also used 
> successfully in libpq.  
> Look for a patch soon.

OK, thanks. Are you planning on spending much time on the project? If
so, do you want commit access?

> > Initially, any work that is undertaken should be supplied 
> to the list 
> > as patches for review following any appropriate discussion. If the 
> > general concencus is that a patch is good, then I will apply it to 
> > CVS.
> 
> Maybe you can start by applying the 64-bit fix patch of the other day?

It only arrived in my inbox this morning for some reason - I'll be
looking at it in a minute.
(Continue reading)

Dave Page | 1 Jul 11:22 2004
Picon

Re: Fixes for 64-bit architectures


> -----Original Message-----
> From: pgsql-odbc-owner <at> postgresql.org 
> [mailto:pgsql-odbc-owner <at> postgresql.org] On Behalf Of Peter Eisentraut
> Sent: 27 June 2004 17:19
> To: pgsql-odbc <at> postgresql.org
> Subject: [ODBC] Fixes for 64-bit architectures
> 
> This patch fixes several misguided assumptions that 
> sizeof(long) == 4, which is not true on 64-bit architectures. 
>  Please install it.

Applied with the following mod in socket.c.

#ifdef WIN32
        UInt4 iaddr;
#else
	in_addr_t iaddr;
#endif

Thanks, Dave.

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
      subscribe-nomail command to majordomo <at> postgresql.org so that your
      message can get through to the mailing list cleanly

K. Balamurugan | 1 Jul 13:09 2004
Picon

Re: Volunteer psqlODBC Developer Required

Dear Project Members of The psqlodbc Project ,

I, Balamurugan, doing my MS (CSE) from IIT madras (www.iitm.ac.in). I can 
spend almost 10 hours per week. If you give me a module with detailed 
requirment spec , I can make the module  with the support of my friend.
Please provide more deatils..

Regards,
Bala

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
      subscribe-nomail command to majordomo <at> postgresql.org so that your
      message can get through to the mailing list cleanly

Ed Brown | 2 Jul 01:05 2004
Picon

Re: ODBC and multi-threading: basics

I work with ODBC from Delphi. Similar environment, different syntax.  The
comments below are not specific to Postgresql, but I have done some threaded
programming with Postgresql specifically.

1) Thread-safety depends on the environment.  I've done some work with
Postgresql, and it appears to be thread-safe, but others know that better
than I.  There's nothing in the ODBC spec that is un-thread-safe.

2) If you need to you should be able to share henv and hdbc. Database
connections are computationally expensive. Definitely create new hstmt's and
don't share them. I have found it a good practice to destroy the connection
and re-establish every 1000-5000 connections. It shouldn't be necessary, but
I've had problems when I didn't, so I just put that as a standard feature in
my libraries and don't think about it any more.

3) Think about the architecture:
- Once, I request an environment handle. (SQLAllocEnv)
- With the environment handle, I get a handle for a database
connection.(SQLAllocConnect
- With this connection, I set the properties and connect.
(SQLSetConnectOption; SQLConnect)
- Once I've connected, I get a handle for a statement.( SQLAllocStm)
- With this statement, I set the properties and execute. (SQLPrepare,
SQLExecute)
- If appropriate, I get the results(SQLFetch, SQLGetData).
- When done, I destroy the statement handle (SQLFreeStmt)
- When I want to execute another statement, I should get another handle. I'm
not saying you have to, but I've had better luck when I do.
- When I'm done, I drop the connection and environment
handles.(SQLDisconnect; SQLFreeConnect; SQLFreeEnv)
(Continue reading)

Dave Page | 2 Jul 10:45 2004
Picon

64 Bit patch (WAS: psqlodbc developer)

Hi Karol,

I've forwarded this patch to the list for review before it's applied (I
don't use IODBC).

Please send any further patches to there as well so they can be properly
reviewed.

Thanks, Dave.

> -----Original Message-----
> From: Karol Szkudlarek [mailto:karol <at> mikronika.com.pl] 
> Sent: 01 July 2004 22:10
> To: Dave Page
> Subject: Re: psqlodbc developer
> 
> I checkout latest cvs trunk and you can't commit the 
> following changes (from my patch.. :-)). I think that should 
> be useful for IODBC version of the driver:
>
>
> diff -x .svn -x stamp-h1 -x .deps -x '*.*[oa]' -x 'config.*' 
> psqlodbc-07.03.0200/iodbc.h psqlodbc-07.03.0200-my/iodbc.h
> 8a9
>  > #include <stdint.h>
> 28,30c29,31
> < typedef signed short SSHOR;
> < typedef short WORD;
> < typedef long DWORD;
> ---
(Continue reading)

Peter Eisentraut | 2 Jul 11:05 2004
Picon
Picon

Re: 64 Bit patch (WAS: psqlodbc developer)

Am Freitag, 2. Juli 2004 10:45 schrieben Sie:
> I've forwarded this patch to the list for review before it's applied (I
> don't use IODBC).

If one uses iODBC then the include files are picked up from the installed 
version of iODBC.  The files iodbc.h, isql.h, etc. in the source tree are 
sort of obsolete.  They are only used for the "neither unixODBC nor iODBC" 
version of the driver, which is quite useless.

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

               http://archives.postgresql.org

Dave Page | 2 Jul 12:14 2004
Picon

Re: 64 Bit patch (WAS: psqlodbc developer)


> -----Original Message-----
> From: Peter Eisentraut [mailto:peter_e <at> gmx.net] 
> Sent: 02 July 2004 10:06
> To: Dave Page
> Cc: pgsql-odbc <at> postgresql.org
> Subject: Re: [ODBC] 64 Bit patch (WAS: psqlodbc developer)
> 
> Am Freitag, 2. Juli 2004 10:45 schrieben Sie:
> > I've forwarded this patch to the list for review before 
> it's applied 
> > (I don't use IODBC).
> 
> If one uses iODBC then the include files are picked up from 
> the installed version of iODBC.  The files iodbc.h, isql.h, 
> etc. in the source tree are sort of obsolete.  They are only 
> used for the "neither unixODBC nor iODBC" 
> version of the driver, which is quite useless.

In which case, should they be removed to force the user to install
either iODBC or unixODBC first?

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

               http://archives.postgresql.org

(Continue reading)

Peter Eisentraut | 2 Jul 16:23 2004
Picon
Picon

Re: 64 Bit patch (WAS: psqlodbc developer)

Am Freitag, 2. Juli 2004 12:14 schrieb Dave Page:
> In which case, should they be removed to force the user to install
> either iODBC or unixODBC first?

This would be the right thing, I think, since I can't see any sense in 
building a "neither" version.  If anyone does, please speak up.

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

               http://archives.postgresql.org


Gmane