On Thu, 20 Jun 2002 [EMAIL PROTECTED] wrote:
> Dan Brown ([EMAIL PROTECTED]) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> can't store {digits} using JDBC
>
> Long Description We are using the JDBC driver, and are losing partial
> data.
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Without showing the database being dumped, the entire output of
> pg_dumpall seems pretty useless so you may as well pipe the whole output
> to /dev/null. I don't think a quiet feature for pg_dumpall has enough
> use for ordinary users. Sorry.
You seem
Hi,
first of all let me tell all of you that PostgreSQL is among the best
in OpenSource!
Unfortunaly there's a (hopefully easy to fix) bug in release 7.2 and
7.2.1 that was not there in 7.1.3 and caused me to switch back today.
Here's the table I'm using (unfortunately I already switched bac
Sorry for the delays on this that machine actually died recently and had to
be rebuit before I could do any more tests.
> > > It would be interesting to see the 'vacuum full analyze'
> > > results for the
> > > system tables in that DB, although perhaps less
> interesting while you
> > > are ru
Thanks, that did fix that problem. Now I have another one. The line:
host all 192.168.1.2 255.255.255.128 password
matches all ip addresses of the form 192.168.1.x. If I change the mask to
255.255.255.255 it no longer matches all addresses. Although this fixes
the problem, it
I have found that !~ and !~* do not match the null string even when one
would expect them to. I am not sure if this is how it is supposed to
work or if this is an error. If this is how it works, I can't figure
out where it is states in the documentation.
Let me give an example. Suppose we h
Hello.
I am working with
PostgreSQL 7.1.2.
Earlier I worked with
PostgreSQL 6.5.3 and I had no problems.
How to make, that at
pg_dump were taken into account sequence. In a file dump.txt it is always
created sequnece with initial value 1.
Example:
I have table:
Users (id serial prim
On Tue, Jun 18, 2002 at 12:02:30PM +0100, Lee Kindness wrote:
> When creating a table in embedded SQL, a foreign key construct like:
> ...
Thanks for the report. I already fixed it in my source tree, but cannot
commit yet due to bison problems.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF
On Thu, 20 Jun 2002, Ingo Ciechowski wrote:
> Unfortunaly there's a (hopefully easy to fix) bug in release 7.2 and
> 7.2.1 that was not there in 7.1.3 and caused me to switch back today.
Nope. It's a bug fix.
> However - if you want to access a =NULL value, it is not found :-((
>
>
>
> i++=# se
On Thu, Jun 20, 2002 at 17:28:31 +0200,
Ingo Ciechowski <[EMAIL PROTECTED]> wrote:
> Hi,
>
> first of all let me tell all of you that PostgreSQL is among the best
> in OpenSource!
>
> Unfortunaly there's a (hopefully easy to fix) bug in release 7.2 and
> 7.2.1 that was not there in 7.1.3 and
Trying to install Postgres version 7.2.1 on Windows2000, using the latest
Cygwin package, just downloaded. Default packages were installed, in addition
to the ones mentioned in 'install.hint' file. When running 'initdb' it hangs
after a few moments.
Output (with --debug option
Ingo Ciechowski <[EMAIL PROTECTED]> writes:
> i++=# select * from uri where freigegeben=NULL;
This is not a bug; the 7.1.* behavior is the bug.
But see transform_null_equals if your application logic depends on
the old non-spec-compliant behavior.
regards, tom lane
On Wed, 19 Jun 2002, David M. Kaplan wrote:
> I have found that !~ and !~* do not match the null string even when one
> would expect them to. I am not sure if this is how it is supposed to
> work or if this is an error. If this is how it works, I can't figure
> out where it is states in the doc
David M. Kaplan wrote:
> Thanks, that did fix that problem. Now I have another one. The line:
>
> hostall192.168.1.2255.255.255.128password
>
> matches all ip addresses of the form 192.168.1.x. If I change the mask
> to 255.255.255.255 it no longer matches all addresses. Alt
"David M. Kaplan" <[EMAIL PROTECTED]> writes:
> I have found that !~ and !~* do not match the null string even when one
> would expect them to.
NULL strings won't match anything. I can't tell whether your row 3 is
an empty string or a NULL --- but if it's a NULL, this behavior is
not a bug. Tr
=?koi8-r?B?8M/Qz9cg4c7E0sXK?= <[EMAIL PROTECTED]> writes:
> I am working with PostgreSQL 7.1.2.
> Earlier I worked with PostgreSQL 6.5.3 and I had no problems.
> How to make, that at pg_dump were taken into account sequence. In a file
> dump.txt it is always created sequnece with initial value 1.
Josemar Dias Ferreira <[EMAIL PROTECTED]> writes:
>Trying to install Postgres version 7.2.1 on Windows2000, using the latest
>Cygwin package, just downloaded. Default packages were installed, in addition
>to the ones mentioned in 'install.hint' file. When running 'initdb' it hangs
>
17 matches
Mail list logo
