On Fri, 7 Mar 2003, Tom Lane wrote:
> Achilleus Mantzios <[EMAIL PROTECTED]> writes:
> > Hi, is there a way to enter integer data by their HEX
> > representation??
>
> I'm not sure that this is SQL-spec, but at least as of 7.3, you can
> coerce a bitstring literal to int, so:
>
> z=# select x'0f
On Fri, 7 Mar 2003, Joe Conway wrote:
> Achilleus Mantzios wrote:
> > Hi, is there a way to enter integer data by their HEX
> > representation??
> >
>
> Is this what you want?
>
> regression=# select x''::int4;
> int4
> ---
> 65535
> (1 row)
Sure. Thanx.
>
>
> Joe
>
--
==
shud use NOT EXISTS instead of NOT IN
as others have suggested .
becoz NOT IN is not very efficient at the moment except
the case on there are small number of items in IN( ... )
regds
mallah.
On Wednesday 12 Mar 2003 2:16 am, Terry Lee Tucker wrote:
> I answered my own question. Yes, it can
i was able to fix the problem but i still dont know the reason. I
discovered the column objectid in table smb_contacts was int4 and not
int8. obviously all values were less then max(int4) dso there was no
problems in that. However I still need to know why the order by trigger
this to happen. I am j
