Skip site navigation (1) Skip section navigation (2)

Re: psqlOdbc Ansi + BDE issues

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Miguel Juan" <mjuan(at)cibal(dot)es>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: psqlOdbc Ansi + BDE issues
Date: 2005-11-19 21:32:05
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4E7E17B@ratbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-odbc
Hi Miguel
 
Unfortunately the installer you supplied is broken. I get some errors
like:
 
Internal error 25001
 
Then when I try to run SQL Explorer, I get:

DbX.DbI was not found or identified.  It is needed to explore databases

:-(
 
Regards, Dave.
 

________________________________

	From: pgsql-odbc-owner(at)postgresql(dot)org
[mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Miguel Juan
	Sent: 15 November 2005 15:08
	To: Dave Page
	Cc: pgsql-odbc(at)postgresql(dot)org
	Subject: Re: [ODBC] psqlOdbc Ansi + BDE issues
	
	
	    Hello,

		----- Original Message ----- 
		From: Dave Page <mailto:dpage(at)vale-housing(dot)co(dot)uk>  
		To: Miguel Juan <mailto:mjuan(at)cibal(dot)es>  ;
pgsql-odbc(at)postgresql(dot)org 
		Sent: Tuesday, November 15, 2005 11:08 AM
		Subject: Re: [ODBC] psqlOdbc Ansi + BDE issues
		
		
		 
		
		

________________________________

			From: pgsql-odbc-owner(at)postgresql(dot)org
[mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Miguel Juan
			Sent: 11 November 2005 12:56
			To: pgsql-odbc(at)postgresql(dot)org
			Subject: [ODBC] psqlOdbc Ansi + BDE issues
			
			
			Hi,
			 
			I'm testing the Ansi version of the
psqlodbc-08.01.0100 and I have found a few isues.
			 
			If you open a table with the BDE SQL explorer,
now it shows all the text fields (char, varchar and text), but for the
TEXT type it show the contents as MEMO. This behavior could be changed
in prior versions  unchecking the "Text as LongVarChar" option and
checking the "Longest" option in the "Unknown Sizes" section.
			 
			Now, it can be fixed only changing the "Max
LongVarchar" edit to 254. It looks like the driver it is not using the
"longest" option in the configuration.
			 

		No - longest doesn't work anymore because there is no
sensible way to figure it out with the libpq driver architecture. It was
only ever there to support pre-6.4 servers that couldn't report the
defined column width (see the config.htm doc for details).
		 
		That aside, shouldn't TEXT equate to MEMO anyway?
		 

	Sure yes, but before (version 7.x) TEXT equate to VARCHAR if the
longest size is under 255 characters, and this change the behavior of
some Delphi components, such as TDataGrid, etc. Anyway, it could be
solved easily with a few lines of code.

			If you open the database schema with the sql
explorer it does not show all the tables, and each table that it shows
appears 6 times. It is easy to reproduce, because it happens with all
the system tables.
			 

		Please try 08.01.0101. 

	Now it shows each system table about four times, and each user
table about three times. Still not showing all the tables in the
database.
	 
	 

		 
		Regards, Dave.

	 
	Regards,
	 
	Miguel Juan
	 
	 
	 

pgsql-odbc by date

Next:From: noreplyDate: 2005-11-21 06:30:30
Subject: [ psqlodbc-Bugs-1000435 ] Special characters in table names
Previous:From: Leendert Paul DiterwichDate: 2005-11-18 14:04:44
Subject: Update: Visual Studio 2005 not happy with postgresql

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group