[BUGS] BUG #3943: ecpg doesn't like "inet" operator

2008-02-08 Thread Arnaud 

The following bug has been logged online:

Bug reference:  3943
Logged by:  Arnaud
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 8.3.0
Operating system:   linux debian etch
Description:ecpg doesn't like "inet" operator
Details: 

This is a sample of my C programm resuming the problem :

***
#include 
#include 

int main()
{
  EXEC SQL BEGIN DECLARE SECTION;

  char *ip_address = "192.168.1.2";
  char ip_result[20];

  EXEC SQL END DECLARE SECTION;

  EXEC SQL WHENEVER SQLWARNING SQLPRINT;

  EXEC SQL CONNECT TO [EMAIL PROTECTED] USER synch IDENTIFIED BY  synch;

  EXEC SQL SELECT text(inet :ip_address) INTO :ip_result;

  EXEC SQL DISCONNECT;

  printf("ip_result: %s\n", ip_result);

  return EXIT_SUCCESS;
}

***

And ecpg returns :
  test_sql.pgc:17: ERROR: syntax error at or near ":ip_address"

This error correpond with "EXEC SQL SELECT inet :ip_address;". If I remove
inet operator it works well. Of course text() does nothing when I remove
inet as postgres doesn't now it is an IP address.

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

   http://archives.postgresql.org

[BUGS] "Password" issues -- bug??

2013-03-03 Thread Louis-Arnaud Iscla 
Hi there,

First off, let me tell you that I've tried successfully the "trust" option in 
pg_hba.conf
I've also searched as much litterature as possible on my issue but it always 
comes down to the pg_hba.conf trick.

It just happens that I cannot connect to the server without the "trust" option 
set. In other words, when I restore md5, I cannot manage to authenticate 
anymore.

Of course, I've done an ALTER USER, triple checked that the password is the 
same, etc. I cannot make it seem to work.

I've tried with both psql and pgAdmin3.

My config:
PostgreSQL 9.0.2
Mac OS 10.7.5

(can locale have something to do with it? Is so, you want to know that I've 
tried with a full C locale for the environment that starts the server + psql, 
as well as with "fr_FR.UTF-8")

Any clue on what this could be?

thanks
Arnaud




-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs