Hello Tom,
it seems that i can't reproduce it too at the moment. When i see the bug
again i will directly send you the data, but it must be something like that:
INSERT INTO benutzer (pnr, vorname, nachname, nutzerkennung, passwort,
plz, ort, strasse, hausnummer, telefon_dienst, telefon_privat
Alexander Strotmann <[EMAIL PROTECTED]> writes:
> Ok, sorry, here it is all:
[ Please keep the mailing list cc'd ]
I couldn't reproduce a problem with these table definitions and some
simple dummy data. Can you see any pattern to when it fails for you
and when it doesn't? What plan do you get f
"Alexander Strotmann" <[EMAIL PROTECTED]> writes:
> we have this table:
> ...
> and this view:
> ...
> So the view joins the upper table with another view
Another view? Don't you think you've left out a lot of information that
would be needed for anyone trying to reproduce this failure? Please
s
Alexander Strotmann wrote:
PostgreSQL version: 8.2
Which version, exactly? Though I don't remember any changes that would
explain this, make sure you run the latest minor version, which is 8.2.7
at the moment.
we get sometimes results where 'bis' is not NULL! But it is not
deterministic be
The following bug has been logged online:
Bug reference: 4106
Logged by: Alexander Strotmann
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: Windows XP / Windows 2003 Server
Description:WHERE - clause in view works only sometimes
Details:
