From: | Tomasz Myrta <jasiek(at)klaster(dot)net> |
---|---|
To: | alien(at)spaceship(dot)com |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: implied FROM |
Date: | 2003-05-02 07:14:46 |
Message-ID: | 3EB21AE6.4020205@klaster.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Dnia 2003-05-02 04:06, Uz.ytkownik Matt Mello napisa?:
<cut>
> So, why doesn't asking for a field from a table that IS NOT in the from
> clause throw an exception? Isn't it violating the SQL language? Why is PG
> implying FROM tables?
>
> Thanks!
Your second case is translated into:
select store.storeid from appliance,store where appliance.applianceid = 32;
There was a discussion several months ago about "missing from clause". I
was voting for changing this warning into exception. Some people said,
that it is very useful inside update queries. The conclusion was this
behaviour should stay as it is. Anyway it isn't such a big problem for
me, because the only problem is to catch "missing from clause" warning.
Regards,
Tomasz Myrta
From | Date | Subject | |
---|---|---|---|
Next Message | Yudha [ Inas_Husband ] Setiawan | 2003-05-02 08:22:47 | It's About field type array |
Previous Message | Oliver Elphick | 2003-05-02 06:16:24 | Re: differences between oracle,pgsql,sybase |