I just replied to this on pgsql-odbc mailing list. Since we're talking
about client performance, please keep the discussion there.
On 09/05/2014 08:54 AM, Vladimir Romanov wrote:
Hello all!
I do some test with ODBC driver for PosgreSql, TimesTen & MySQL. I compare
performance on very simple req
Hello all!
I do some test with ODBC driver for PosgreSql, TimesTen & MySQL. I compare
performance on very simple request. Database always located on same PC as
test application. Test PC - Lenovo T500, Cnetos 6.5 64, 8 Gb RAM, SSD.
I found what PostgreSql ODBC driver is slowest in comparison.
IMHO p
Hot sure if this is the right list, but. . .
On Mon, Sep 02, 2002 at 08:20:14PM -0400, Vince Vielhaber wrote:
> On Sat, 31 Aug 2002, Marc G. Fournier wrote:
>
> >
> > This is all in Vince's area ...
>
> Correction. You're not looking, it's in the users lounge. We've
> covered the button thing
On Sat, 31 Aug 2002, Marc G. Fournier wrote:
>
> This is all in Vince's area ...
Correction. You're not looking, it's in the users lounge. We've
covered the button thing already.
>
>
> On 23 Aug 2002, Greg Copeland wrote:
>
> > I must be blind. I don't see links to gborg anywhere on the deve
On Sat, 31 Aug 2002, Marc G. Fournier wrote:
>
> This is all in Vince's area ...
You're right. You don't see 'em.
>
>
> On 23 Aug 2002, Greg Copeland wrote:
>
> > I must be blind. I don't see links to gborg anywhere on the developer
> > or main site web pages. Perhaps more obvious a sister s
This is all in Vince's area ...
On 23 Aug 2002, Greg Copeland wrote:
> I must be blind. I don't see links to gborg anywhere on the developer
> or main site web pages. Perhaps more obvious a sister site link would
> be of value.
>
> The only link I found was under "User's Lounge" and then "Po
Julian Mehnle wrote:
>
> Yeah, it does *not* exhibit the faulty CRLF<->LF conversion behavior.
> Is this a custom build of the ODBC driver done by you? Will the
> official driver be fixed soon?
I would commit the fix to cvs this week.
regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue
Hiroshi Inoue <[EMAIL PROTECTED]> wrote:
> Julian Mehnle <[EMAIL PROTECTED]> wrote:
> > Recently I tried to use the new 7.02.0001 Win32 ODBC driver in the new
> > (beta) Unicode mode in conjunction with MS Access 2000 and a "UNICODE"
> > encoded database stored in a PostgreSQL 7.2.1 database runnin
Julian Mehnle wrote:
>
> Hiroshi Inoue <[EMAIL PROTECTED]> wrote:
> > Julian Mehnle <[EMAIL PROTECTED]> wrote:
> > > Recently I tried to use the new 7.02.0001 Win32 ODBC driver
> > > in the new (beta) Unicode mode in conjunction with MS Access
> > > 2000 and a "UNICODE" encoded database stored in
"Julian Mehnle, Linksystem Muenchen" wrote:
>
> Hi all!
>
> Recently I tried to use the new 7.02.0001 Win32 ODBC driver in the new
> (beta) Unicode mode in conjunction with MS Access 2000 and a "UNICODE"
> encoded database stored in a PostgreSQL 7.2.1 database running on a
> Linux system.
>
> I
Hiroshi Inoue <[EMAIL PROTECTED]> wrote:
> Julian Mehnle <[EMAIL PROTECTED]> wrote:
> > Recently I tried to use the new 7.02.0001 Win32 ODBC driver in the new
> > (beta) Unicode mode in conjunction with MS Access 2000 and a "UNICODE"
> > encoded database stored in a PostgreSQL 7.2.1 database runni
Hi all!
Recently I tried to use the new 7.02.0001 Win32 ODBC driver in the new
(beta) Unicode mode in conjunction with MS Access 2000 and a "UNICODE"
encoded database stored in a PostgreSQL 7.2.1 database running on a
Linux system.
I noticed that when the "LF<->CRLF Conversion" option is *enable
Julian Mehnle wrote:
> [...] I made a patch.
>
> ==8<==snip==
> [word-wrapped patch]
> ==snip==>8==
Doh!
I swear I told my news reader not to word-wrap exactly this message,
but it wrapped it anyway.
Hi Gowey,
Please post to pgsql-odbc list if the problem is ODBC
specific.
"Gowey, Geoffrey" wrote:
>
> Two problems (I've been holding back reporting until I ran into this
> second):
>
> Background: I'm trying to migrate an existing db from MS Sql 2K to pgsql by
> creating a DTS job.
>
> DB sys
Two problems (I've been holding back reporting until I ran into this
second):
Background: I'm trying to migrate an existing db from MS Sql 2K to pgsql by
creating a DTS job.
DB system info: NT 4 sp6a, MS SQL2K Regular, Pgsql ODBC driver 7.01.00.06.
First problem: The ODBC driver reports a colum
I installed the ODBC driver for Postgre, and linked in a table which has a
Serial field for the primary key. In MS Access, the type is shown as just
"Number (long integer)".
When I try to add new records to my database in Access, I don't put anything
into the key field because the server is suppo
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]]
> Sent: 16 January 2001 16:50
> To: Dave Page
> Cc: '[EMAIL PROTECTED]'
> Subject: Re: [HACKERS] ODBC Driver int8 Patch
>
>
> As I remember, the problem is that this makes us mat
As I remember, the problem is that this makes us match the ODBC v2 spec,
but then we would not match the v3 spec. Is that correct?
[ Charset ISO-8859-1 unsupported, converting... ]
> Hi,
>
> It was suggested that I post this patch here as no notice was taken of it
> when posted to interfaces!
Hi,
It was suggested that I post this patch here as no notice was taken of it
when posted to interfaces!
This fixes problems with int8 columns which are reported by the driver as
SQL_BIGINT rather than SQL_CHAR as per the ODBC v2 spec. Specifically, I
have had problems with MS ADO - any queries
I am curious as to where the newest ODBC driver source is -- I retrieved
/src/interfaces/odbc from CVS, but it appeared to only be version
6.40.0009 and was lacking the Visual C++ workspace/project files that
were in the 6.50. release zip file on the FTP server.
Thanks
Michael Fork - CCNA
20 matches
Mail list logo
