On Fri, Aug 28, 2009 at 05:03, Alvaro Herreraalvhe...@commandprompt.com wrote:
Robert Haas escribió:
2009/8/27 Alvaro Herrera alvhe...@commandprompt.com:
Robert Haas escribió:
Para obtener ayuda en espan~ol, tal vez puede Ud. tratar
pgsql-es-ay...@postgresql.org. Creo que no tenemos una
On Thu, Aug 27, 2009 at 19:41, Tom Lanet...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
2009/8/27 Tom Lane t...@sss.pgh.pa.us:
Magnus Hagander mag...@hagander.net writes:
Fix applied - exports.txt had a tab in it, instead of spaces, to
separate the field from the number.
The following bug has been logged online:
Bug reference: 5020
Logged by: Helena Biander
Email address: hebiguard-s...@yahoo.se
PostgreSQL version: 8.4
Operating system: WinXP
Description:Stackbuilder not functioning
Details:
When trying to run stackbuilder at
On Fri, Aug 28, 2009 at 4:01 AM, Helena Bianderhebiguard-s...@yahoo.se wrote:
The following bug has been logged online:
Bug reference: 5020
Logged by: Helena Biander
Email address: hebiguard-s...@yahoo.se
PostgreSQL version: 8.4
Operating system: WinXP
Description:
Magnus Hagander escribió:
On Fri, Aug 28, 2009 at 05:03, Alvaro Herreraalvhe...@commandprompt.com
wrote:
It would be good, but currently that list comes from a database that
cannot handle external lists. Since that database also powers the
search engine, I am very afraid to touch it ...
The following bug has been logged online:
Bug reference: 5021
Logged by: Dan O'Hara
Email address: danarasoftw...@gmail.com
PostgreSQL version: 8.3.7
Operating system: win32
Description:ts_parse doesn't recognize email addresses with
underscores
Details:
In the
Today I ran into a problem relating to $subject. plpgsql's handling
of 'null' composite types is not consistent with what you get in sql:
create table foo(a text, b text);
create table bar(id int, f foo);
insert into bar values (1, ('a', 'b'));
create or replace function f(_foo out foo) returns
Merlin Moncure mmonc...@gmail.com writes:
Today I ran into a problem relating to $subject. plpgsql's handling
of 'null' composite types is not consistent with what you get in sql:
Hm. It looks like plpgsql treats composite arguments as being row
instead of record variables, which has some
On Wed, Aug 26, 2009 at 5:55 AM, Isharaishara...@gmail.com wrote:
The following bug has been logged online:
Bug reference: 5013
Logged by: Ishara
Email address: ishara...@gmail.com
PostgreSQL version: 8.4
Operating system: Solaris x86
Description: Error in
Merlin Moncure mmonc...@gmail.com wrote:
This leads to some very weird behaviors, for example 'coalesce(foo,
something)' and 'case when foo is null then something else foo end'
can give different answers.
Quite apart from the issue you're pursuing, this is another example of
how the
On Fri, Aug 28, 2009 at 1:38 PM, Kevin
Grittnerkevin.gritt...@wicourts.gov wrote:
Merlin Moncure mmonc...@gmail.com wrote:
This leads to some very weird behaviors, for example 'coalesce(foo,
something)' and 'case when foo is null then something else foo end'
can give different answers.
On Fri, Aug 21, 2009 at 9:35 AM, Pramodpramodchoudhar...@yahoo.com wrote:
The following bug has been logged online:
Bug reference: 5003
Logged by: Pramod
Email address: pramodchoudhar...@yahoo.com
PostgreSQL version: 8.4.0-1
Operating system: Windows XP
Description:
The following bug has been logged online:
Bug reference: 5022
Logged by: Tyler Burd
Email address: tb...@cudc.org
PostgreSQL version: 8.4
Operating system: Windows Server 2008
Description:unkown winsock error 10061
Details:
Upgraded from 8.3.4 to 8.4, and we
13 matches
Mail list logo
