[GENERAL] Trying to install ODBC driver on Windows XP notebook
I have latest Postgresql installed on a notebook and now trying to install the driver which I have downloaded and run so that it is now available in the ODBC Data Source Administrator This machine has CA security suite, latest version installed and I have added a network rule that allows all applications using TCP and UDP on Port 4532 to gain access In and Out I have the correct database name and get the following message when I try to Test the connection. Could not connect to the server No Connection could be made because the target machine actively refused it. (192.168.1.7:5432) I don't know what else I can now do to get the connection. Any suggestions would be appreciated. Cheers Phil Jackson -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Cannot open table in new database
We've set up a Sql database for the first time and get an error reported back to our application from the ODBC session object when we try to open one of the tables. [42p01][7]ERROR Relation "SqlAnal" does not exist; table not found! Here is my database outline in the Admin tool Servers(1) Concept Patterns (localhost:5432) Databases(1) Postgres casts languages schemas Public - - Tables(2) DocHeader SqlAnal Replication Tablespaces(2) pg_default pg_global Group Roles Login Roles(1) Concept We can access the list of tables from the ODBC driver which shows the above tables. We've obviously done something wrong but we don't know where to look. The Help button is not helpful at all. Any ideas on what we are doing incorrectly? Cheers Phil Jackson -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Cannot open table in new database
Hi Adrian The link says that; "Identifier and key word names are case insensitive." But I have renamed the source table in lowercase and this gets me one step further. I'll carry on and see what happens next. Cheers Phil Jackson On 6/30/2010 3:18 PM, Adrian Klaver wrote: On 07/01/2010 09:46 AM, Phil Jackson wrote: We've set up a Sql database for the first time and get an error reported back to our application from the ODBC session object when we try to open one of the tables. [42p01][7]ERROR Relation "SqlAnal" does not exist; table not found! Here is my database outline in the Admin tool Servers(1) Concept Patterns (localhost:5432) Databases(1) Postgres casts languages schemas Public - - Tables(2) DocHeader SqlAnal Replication Tablespaces(2) pg_default pg_global Group Roles Login Roles(1) Concept We can access the list of tables from the ODBC driver which shows the above tables. We've obviously done something wrong but we don't know where to look. The Help button is not helpful at all. Any ideas on what we are doing incorrectly? Cheers Phil Jackson Using mixed case :) See here for gotchas of using mixed case: http://www.postgresql.org/docs/8.4/interactive/sql-syntax-lexical.html 4.1.1. Identifiers and Key Words -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Cannot open table in new database
Hi Adrian I had missed that bit. That makes sense now. Cheers Phil Jackson On 6/30/2010 5:04 PM, Adrian Klaver wrote: On Thursday 01 July 2010 11:11:29 am Phil Jackson wrote: Hi Adrian The link says that; "Identifier and key word names are case insensitive." But I have renamed the source table in lowercase and this gets me one step further. I'll carry on and see what happens next. Cheers Phil Jackson You need to go to bottom of that section where you would find :) "Quoting an identifier also makes it case-sensitive, whereas unquoted names are always folded to lower case. For example, the identifiers FOO, foo, and "foo" are considered the same by PostgreSQL, but "Foo" and "FOO" are different from these three and each other. (The folding of unquoted names to lower case in PostgreSQL is incompatible with the SQL standard, which says that unquoted names should be folded to upper case. Thus, foo should be equivalent to "FOO" not "foo" according to the standard. If you want to write portable applications you are advised to always quote a particular name or never quote it.) " -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Problems with ODBC Driver
I have a notebook that I am using as a server for testing purposes and it has the official ODBC driver installed. I can access this and use it connect to PostreSql. On a second machine on the same network - I also have the same ODBC driver installed. The behaviour of this one is quite different. I have a test program that works on the server but when I run it on this workstation, it can create a file with a couple of fields which I can verify by looking inside PostgreSQL. But when I go to open up that file and refer to one of its fields, I get an error message saying the field doesn't exist. I am running XP Professional on both machines. I have no idea what is happening - I have opened up the firewall on both machines to allow port 5432 to be used by all applications with TCP (also tried TCP and UDP). Does anyone have any suggestions? Cheers Phil Jackson -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Problems with ODBC Driver
Hi Hiroshi The same program works on the server unchanged - that's why I think it is something to do with the driver. The error message says that the field name doesn't exist when it does as can be verified by looking at the database in Postgresql. Cheers Phil Jackson On 9/2/2010 3:19 AM, Hiroshi Saito wrote: Hi. There is very little information which explores a problem. What thing is an actual error message? The following is my imagination As for specific field, it may be the LOWER problem of a character. example) -- CREATE TABLE xx("Field" TEXT); postgres=# SELECT Field FROM xx; ERROR: column "field" does not exist LINE 1: SELECT Field FROM xx; postgres=# SELECT "Field" FROM xx; Field --- (0 rows) If my misunderstand, the error message which you show will be able to be solved. Regards, Hiroshi Saito - Original Message - From: "Phil Jackson" I have a notebook that I am using as a server for testing purposes and it has the official ODBC driver installed. I can access this and use it connect to PostreSql. On a second machine on the same network - I also have the same ODBC driver installed. The behaviour of this one is quite different. I have a test program that works on the server but when I run it on this workstation, it can create a file with a couple of fields which I can verify by looking inside PostgreSQL. But when I go to open up that file and refer to one of its fields, I get an error message saying the field doesn't exist. I am running XP Professional on both machines. I have no idea what is happening - I have opened up the firewall on both machines to allow port 5432 to be used by all applications with TCP (also tried TCP and UDP). Does anyone have any suggestions? Cheers Phil Jackson -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general