[BUGS] BUG #3635: libpg.dll localization change
2007-09-26
Thread
libpg.dll problem while changing from version 8.2.4 no-installer to 8.2.5 no-installer
The following bug has been logged online: Bug reference: 3635 Logged by: libpg.dll problem while changing from version 8.2.4 no-installer to 8.2.5 no-installer Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2.5 Operating system: Intel Pentium D 2,6 GHZ, 1 GB RAM, Wind
Re: [BUGS] Crash 8.2.5 backend using tsearch2
is some other bug involved too. But I would say that compareWORD is broken nonetheless. Fixed, you are right. -- Teodor Sigaev E-mail: [EMAIL PROTECTED] WWW: http://www.sigaev.ru/ ---(
Re: [BUGS] BUG #3619: Renaming sequence does not update its 'sequence_name' field
I am confused by this bug report. Please show us the CREATE TABLE that goes with it. --- Guillaume 'ioguix' de Rorthais wrote: > > The following bug has been logged online: > > Bug reference: 3619 > Logged by:
Re: [BUGS] BUG #3619: Renaming sequence does not update its 'sequence_name' field
I created this bug report using the pagila db sample ( http://pgfoundry.org/projects/dbsamples/ ). Here is how the sequence and table are created : ~ CREATE SEQUENCE actor_actor_id_seq START WITH 1 INCREMENT BY 1 NO MAXVALUE NO
Re: [BUGS] BUG #3619: Renaming sequence does not update its 'sequence_name' field
ioguix <[EMAIL PROTECTED]> writes: > br3619=# CREATE SEQUENCE sample_seq_to_rename; > CREATE SEQUENCE > br3619=# select sequence_name from sample_seq_to_rename; > sequence_name > -- > sample_seq_to_rename > (1 ligne) > br3619=# ALTER TABLE sample_seq_to_rename RENAME TO sa
Re: [BUGS] BUG #3619: Renaming sequence does not update its 'sequence_name' field
Tom Lane wrote: > ioguix <[EMAIL PROTECTED]> writes: > > br3619=# CREATE SEQUENCE sample_seq_to_rename; > > CREATE SEQUENCE > > br3619=# select sequence_name from sample_seq_to_rename; > > sequence_name > > -- > > sample_seq_to_rename > > (1 ligne) > > > br3619=# ALTER TAB
Re: [BUGS] BUG #3619: Renaming sequence does not update its 'sequence_name' field
Alvaro Herrera <[EMAIL PROTECTED]> writes: > I am amused by the fact that we store the sequence name in the sequence > itself though. Yeah, it's a bit pointless. One possible response to this gripe would be to take the name out of the sequence itself. However, that would likely break client-side
Re: [BUGS] BUG #3619: Renaming sequence does not update its 'sequence_name' field
Tom Lane wrote: > Alvaro Herrera <[EMAIL PROTECTED]> writes: >> I am amused by the fact that we store the sequence name in the sequence >> itself though. > > Yeah, it's a bit pointless. One possible response to this gripe would > be to take the name out of the sequence itself. However, that woul
[BUGS] BUG #3636: createNativeQuery - don't work with INSERT INTO.
The following bug has been logged online: Bug reference: 3636 Logged by: Michael "Zorkus" Antonov Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2.* Operating system: Fedora Core 7, kernel 2.6.22.4-64.fc7, x86-32 Description:createNativeQuery - don't work with
Re: [BUGS] BUG #3636: createNativeQuery - don't work with INSERT INTO.
"Michael "Zorkus" Antonov" <[EMAIL PROTECTED]> writes: > i receive this message - > Exception [TOPLINK-4002] (Oracle TopLink Essentials - 2006.8 (Build > 060830)): oracle.toplink.essentials.exceptions.DatabaseException > Internal Exception: org.postgresql.util.PSQLException: ERROR: > повÑоÑ