On 02/02/2010 10:23 PM, Tom Lane wrote:
> Joe Conway writes:
>> Should I also be looking to replace all (or most) other instances of
>> PQsetdbLogin()?
>
> I think we at least wanted to fix pg_dump(all)/pg_restore. Not sure if
> the others are worth troubling over.
OK, this one includes pg_dump
On Wed, Feb 3, 2010 at 9:46 PM, Daniel J. Baldev wrote:
> All I want to do is to delete a database, but I don't know how to actually
> input the dropdb command and what other stuff I need to open...can you help?
> I think my problem will be very simple for someone who understands this
I probably
All I want to do is to delete a database, but I don't know how to actually
input the dropdb command and what other stuff I need to open...can you help?
I think my problem will be very simple for someone who understands this
--
From: "Robert Haas"
On Wed, Feb 3, 2010 at 9:32 PM, Dan Baldev wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5312
> Logged by: Dan Baldev
> Email address: dbal...@msn.com
> PostgreSQL version: 8.4
> Operating system: Windows Vista
> Description: I NEED HELP
> Deta
The following bug has been logged online:
Bug reference: 5312
Logged by: Dan Baldev
Email address: dbal...@msn.com
PostgreSQL version: 8.4
Operating system: Windows Vista
Description:I NEED HELP
Details:
I USE POSTGRES AND I AM A LAYMAN. I HAVE TRIED LOOKING EVERYW
Tom Lane wrote:
> Alvaro Herrera writes:
> > Bruce Momjian escribi?:
> >> I found one place in the docs where this wasn't immediately clear, so I
> >> applied the attached documentation patch.
>
> > I liked Tom's suggestion better, because then you don't start
> > questioning about quoting key wo
Alvaro Herrera writes:
> Bruce Momjian escribió:
>> I found one place in the docs where this wasn't immediately clear, so I
>> applied the attached documentation patch.
> I liked Tom's suggestion better, because then you don't start
> questioning about quoting key words or not.
Yes, exactly, tha
Bruce Momjian escribió:
> I found one place in the docs where this wasn't immediately clear, so I
> applied the attached documentation patch.
I liked Tom's suggestion better, because then you don't start
questioning about quoting key words or not.
> --- 144,150
>case sensitivity
>
Robert Haas wrote:
> On Wed, Feb 3, 2010 at 2:36 PM, Chris Travers wrote:
> > I don't like the proposed wording though. ?I would suggest something more
> > like:
>
> Just to be clear, that's the actual wording, not a proposal.
I found one place in the docs where this wasn't immediately clear, s
On Mon, Feb 1, 2010 at 11:28 AM, Cristian wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5305
> Logged by: Cristian
> Email address: cbit...@gmail.com
> PostgreSQL version: 8.3.9
> Operating system: Windows 2003 Server Standard x64
> Description:
On Wed, Feb 3, 2010 at 2:36 PM, Chris Travers wrote:
> I don't like the proposed wording though. I would suggest something more
> like:
Just to be clear, that's the actual wording, not a proposal.
...Robert
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to yo
Tom Lane wrote:
> "Key words and unquoted identifiers are case insensitive..."
FWIW, that is the *exact* rewording that came to mind for me as a
possible solution.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgr
Chris Travers wrote:
> It is probably understandable that some people
> would miss it (I did, a moment ago, until you mentioned it).
That seems like pretty good evidence that a footnote or
qualification of the initial statement would occasionally save some
confusion.
-Kevin
--
Sent via pgs
Chris Travers writes:
> On Wed, Feb 3, 2010 at 11:37 AM, Tom Lane wrote:
>> Kelly SACAULT writes:
>>> ".. Identifier and key word names are case insensitive..."
>>
>> You need to not stop reading at that point, but continue on to the part
>> that explains how quoted identifiers work.
> The onl
On Wed, Feb 3, 2010 at 11:37 AM, Tom Lane wrote:
> Kelly SACAULT writes:
>> Here is what I read from the officiel manual :
>> http://www.postgresql.org/docs/8.0/static/sql-syntax.html
>> stating that :
>> ".. Identifier and key word names are case insensitive..."
>
> You need to not stop reading
On Wed, Feb 3, 2010 at 11:30 AM, Robert Haas wrote:
> 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 th
Kelly SACAULT writes:
> Here is what I read from the officiel manual :
> http://www.postgresql.org/docs/8.0/static/sql-syntax.html
> stating that :
> ".. Identifier and key word names are case insensitive..."
You need to not stop reading at that point, but continue on to the part
that explains ho
On Wed, Feb 3, 2010 at 2:13 PM, Kelly SACAULT wrote:
> Here is what I read from the officiel manual :
> http://www.postgresql.org/docs/8.0/static/sql-syntax.html
>
> stating that :
> ".. Identifier and key word names are case insensitive..."
>
> This is not the truth at all and I think that this s
Hi Pavel, and Chris,
Thank you both your yours responses.
Here is what I read from the officiel manual :
http://www.postgresql.org/docs/8.0/static/sql-syntax.html
stating that :
".. Identifier and key word names are case insensitive..."
This is not the truth at all and I think that this stateme
"Lothar Bongartz" writes:
> A "NOT FOUND" condition in a stored function throws a "GetData to Procedure
> return failed." error, which cannot be trapped by the EXCEPTION handling.
There is no such error message text anywhere in Postgres, and you
haven't given enough context to let anyone guess wh
2010/2/3 Lothar Bongartz :
>
> The following bug has been logged online:
>
> Bug reference: 5310
> Logged by: Lothar Bongartz
> Email address: lotharbonga...@hotmail.com
> PostgreSQL version: 8.4
> Operating system: Windows XP Professioanl
> Description: "NOT FOUND" thro
The following bug has been logged online:
Bug reference: 5310
Logged by: Lothar Bongartz
Email address: lotharbonga...@hotmail.com
PostgreSQL version: 8.4
Operating system: Windows XP Professioanl
Description:"NOT FOUND" throws "GetData to Procedure return failed."
in
The following bug has been logged online:
Bug reference: 5311
Logged by: John
Email address: jglas...@globaltv.com
PostgreSQL version: 8.3.9-1
Operating system: Windows XP
Description:Won't install.
Details:
When I run the installation, I get the following error mes
PHP Script:
";
$s = "DROP TABLE t123;"; // table doesn't exist
pg_send_query($c, $s);
$r = pg_get_result($c);
echo "Source function: " . pg_result_error_field($r,
PGSQL_DIAG_SOURCE_FUNCTION) . "";
pg_close($c);
}
if($c = pg_connect("host=192.168.0.60 dbname=xxx user=xxx password=xxx
por
24 matches
Mail list logo
