A logical field (Yes/No) in MS Access was exported as bpchar in Postgres.
I failed to find this data type in the User's Manual. Only bool is mentioned
there.
Please advise.
Thanks,
Mihai
Error return is that it is not able to find the attribute
"any_column_name" in the table.
This maybe obvious but have you looked at the table layout to see if the
column exists. You may have a problem with spaces in the name or upper case
letters in the name. In either case you must quote
mikeo wrote:
just a curiosity question...is the pg_FieldType() function
something you wrote yourself?
It's a PHP function.
-Ron-
Sorry, but i made a mistake here !
the function dept or is equivalente coud not solve this problem (pass a
table name as a parameter)
In Oracle exist Dynamic SQL, is there something like that in postgres ?
Is it possible to execute a query built in a plpgsql function or do we
need to use Perl
Thanks for the response:
The column exists in the table structure and can be accessed/queried via
psql with SELECT statements or via ODBC SELECT statements form Access97.
The data intergrity (content) for the table and columns is fine and intact.
The psql CREATE INDEX statement can't see the
[EMAIL PROTECTED] writes:
The psql CREATE INDEX statement can't see the imported column
(name/attribute)... wierd?
I still think that Bryan's got the right idea --- Access probably
created the column name with some embedded blanks and/or upper-case
characters, which'd mean that you have to
I've run across yet another cause that can make Postgres not be able to
bind to the port it desires (or any other port, for that matter). I don't
recall it being discussed before, so I'll throw it out.
When postgres binds to any port, it likes to write a file in /tmp, along
the lines of
"Steve Wolfe" [EMAIL PROTECTED] writes:
When postgres binds to any port, it likes to write a file in /tmp, along
the lines of ".s.PGSQL.5432". If /tmp is not writeable by the postgres
process, it will not be able to bind to any port. However, it doesn't give
you an intelligent error
I tried this and got what I thought was a fairly reasonable error
message:
FATAL: StreamServerPort: bind() failed: Permission denied
Is another postmaster already running on that port?
If not, remove socket node (/tmp/.s.PGSQL.5432) and retry.
postmaster: cannot create UNIX
