Hi,
thank you for the short explanation of the problem.
I'am trying to rewrite this query into another to get out the
subselect...
thanks as
Brian McCane schrieb:
>
> Your problem is probably type-casting related. The result of the
> sub-select is most likely an ::int32 and doesn't work when
Dear Guys,
May I have a question about the authorization of psql?
By using '\z' in psql context, I can get the description of authorization about each
table/view.
r -- SELECT
w -- UPDATE/DELETE
a -- INSERT
R -- RULE
raja kumar thatte <[EMAIL PROTECTED]> writes:
> I want to know how the--where condition--is executed in a sql query.
> e.g., select aa,bb,cc from ttt where aa=100 and bb = 200 and cc =300.
> my doubt is , will psql leave the record as on when it fails to satisfy a record
>having aa !=100
> or w
Hai every body,
I want to know how the--where condition--is executed in a sql query.
e.g., select aa,bb,cc from ttt where aa=100 and bb = 200 and cc =300.
my doubt is , will psql leave the record as on when it fails to satisfy a record having aa !=100
or will it chect for bb = 200 and cc = 300 a
Hi,
After a few tests my conclusion is:
- This problem only accist if you use UNICODE and use a char record
(SQL_ASCII works fine).
- I think the problem is that de character counter count special characters
differend from normal characters. It only occur when you insert a string
which size is
Hi,
i have a simple question on indices and subselects.
Lets say i have a table foo with a column id int8 as primary_key bar.
If i do a
select * from foo where id = 10 then the index bar is used.
if i do
select * from foo where id in (10,20) then the index is used.
but if id do
select * from
See techdocs performance article:
http://techdocs.postgresql.org
Martins Zarins wrote:
> On 18 Jan 2002, at 9:22, Jeremy Buchmann wrote:
> >
> > It's more than just processor cache, it's your whole I/O subsystem.
> > How fast are your drives? How fast is the drive controller? How much
Hi,
I have a problem with inserting/updating "strange" characters. I can only use
strange characters at the beginning of a string. The select statement has'nt
this problem.
Is this a bug or am i doing something wrong ?
Regards,
Ferdinand
Example:
db=> select '\353x';
?column?
--
On 18 Jan 2002, at 9:22, Jeremy Buchmann wrote:
>
> It's more than just processor cache, it's your whole I/O subsystem.
> How fast are your drives? How fast is the drive controller? How much
> cache is on each drive? How much cache is on the drive controller?
> Are you going to use a RAID? If
