On Tue, Jan 30, 2007 at 04:41:13PM -0200, Ezequias Rodrigues da Rocha wrote:
> So you are tell me that it is impossible to retrieve it ok ?
No.
> Just by changing this values (what I did now) it is possible to get
> the error messages and their statements OK?.
Yes, but you need to signal the po
> On Tue, Jan 30, 2007 at 02:38:07PM +0100, Bart Degryse wrote:
>
>> Andrew, I think you're wrong stating that Oracle would interpret
>> NULL and empty string as equal. The Oracle databases I use (8, 9
>> and 10) certainly make a distiction between both values. Maybe
>> earlier versions did so, th
D'Arcy J.M. Cain wrote:
>SELECT * FROM table WHERE column IS NULL;
>SELECT * FROM table WHERE column = NULL;
>
> The latter violates the SQL spec and is not allowed by PostgreSQL
> without setting a special flag.
It doesn't violate any spec and it's certainly allowed by PostgreSQL
without
Andrew Sullivan wrote:
AFAIK they don't accept the latter any more than we do. But again,
I'm an Oracle ignoramous. I _do_ know that people of my acquaintance
who have historically only developed against Oracle have given me
queries with things like
value = ''
in it, and been surpr
So you are tell me that it is impossible to retrieve it ok ?
Just by changing this values (what I did now) it is possible to get
the error messages and their statements OK?.
My best Regards
Ezequias
2007/1/30, Andrew Sullivan <[EMAIL PROTECTED]>:
On Tue, Jan 30, 2007 at 03:01:05PM -0200, Ezequ
On Tue, Jan 30, 2007 at 03:01:05PM -0200, Ezequias Rodrigues da Rocha wrote:
> I know there are many logs in postgresql but I don't have many
> familiarity with all them.
It's not totally plain what you want to have happen -- whether you
want all queries, whether you merely want ERRORs to show up
Hi list,
I lost some data becouse my application does not throws an exception
when an update statement report an error.
It is possible to find out if the PostgreSQL could have this error
(and more important the complete statement that make this errors
occurs) ?
I know there are many logs in pos
On Tue, Jan 30, 2007 at 11:38:34AM -0500, D'Arcy J.M. Cain wrote:
> I don't have an Oracle installation here and I haven't used it much but
> I wonder if they treat the following two statements differently.
>
>SELECT * FROM table WHERE column IS NULL;
>SELECT * FROM table WHERE column = NU
On Tue, 30 Jan 2007 09:23:32 -0500
Andrew Sullivan <[EMAIL PROTECTED]> wrote:
> Hmm. Well, I'm not an Oracle guy, so I don't really know. All I
> know is that we occasionally get people coming from Oracle who are
> surprised by this difference. What I've been _told_ is that '' and
> NULL are und
Hi list,
I don't know how it occurs but in some way my work and test databases
are connected.
If I drop my work database the test database is dropped and vice
versa. I suppose it occurs becouse I am mantaining this two databases
making the following.
- Backup the main database (work)
- Resto
Andrew Sullivan Wrote:
> On Tue, Jan 30, 2007 at 02:38:07PM +0100, Bart Degryse wrote:
> > Andrew, I think you're wrong stating that Oracle would interpret
> > NULL and empty string as equal. The Oracle databases I use (8, 9
> > and 10) certainly make a distiction between both values. Maybe
> > ea
On Tue, Jan 30, 2007 at 02:38:07PM +0100, Bart Degryse wrote:
> Andrew, I think you're wrong stating that Oracle would interpret
> NULL and empty string as equal. The Oracle databases I use (8, 9
> and 10) certainly make a distiction between both values. Maybe
> earlier versions did so, that I don
Andrew, I think you're wrong stating that Oracle would interpret NULL and empty
string as equal.
The Oracle databases I use (8, 9 and 10) certainly make a distiction between
both values.
Maybe earlier versions did so, that I don't know.
>>> Andrew Sullivan <[EMAIL PROTECTED]> 2007-01-30 14:13 >>
On Tue, Jan 30, 2007 at 04:32:22PM +1100, Phillip Smith wrote:
> SHAMPOO","EQUEST","401600","0.00","0.00","0.00","0.00","10.00",""
^^
> SELECT * FROM tmpstk WHERE ean = NULL;
Along
Hello everyone.
Can anyone tell me how I can test for the occurrence of an array in an
array? Intuitively, this should work:
SELECT ARRAY[1,2,3] = ANY(ARRAY[[1,2,3],[2,3,4]]);
However, this gives me "operator does not exist: integer[] = integer".
I'm running 8.2.
--
Niklas Bergius
--
15 matches
Mail list logo