dear all...
SELECT FROM SO_DEL DEL
WHERE DEL.SALES_CCN = :SALES_CCN
AND EXISTS (SELECT 'X' FROM SO LIN
WHERE LIN.SALES_CCN = DEL.SALES_CCN)
guys...
any idea on the select 'X' part?
why I change it to select TRUE from SO LIN and is still works fine?
is that just a dummy variable?
Click the link below to see the new game I'm developing!
SQL in PROIV SL
Started by
siobi
, Sep 29 2004 06:38 AM
12 replies to this topic
#2
Rob Donovan
-
- Admin
-
- 1,652 posts
rob@proivrc.com
- Gender:Male
- Location:Spain
Posted 29 September 2004 - 06:48 AM
Hi,
Yes its just a dummy value, so that the EXISTS statement gets something to test against.
Rob D.
Yes its just a dummy value, so that the EXISTS statement gets something to test against.
Rob D.
#7
CSuarezdelReal
-
- Members
-
- 91 posts
Advanced
- Gender:Not Telling
Posted 30 September 2004 - 12:55 PM
In theory you can replace any SEL-XXX by a SQL SELECT statement that might return rows or in any Before Read logic, where you might define table keys. Depending on the ProIVKernel version and the DBMS you use some of them do not work but usually it is just a matter of knowing what you want, code the SQL statement you know would give you the result, and if that does not work, try an alternate SQL statement.
Most of the times I get the result in the first trail. I have used very complex queries to multiple tables, unions, dummy tables, sorting and so forth, and they work great, saving a few LS and gaining noticeable response time.
Most of the times I get the result in the first trail. I have used very complex queries to multiple tables, unions, dummy tables, sorting and so forth, and they work great, saving a few LS and gaining noticeable response time.
Claudio Suarez del Real "It is not the strongest of the species that survive, nor the most intelligent, but the ones most responsive to change."
#8
Vol Yip
-
- Members
-
- 393 posts
ProIV Guru
- Gender:Male
- Location:Hong Kong
Posted 30 September 2004 - 01:08 PM
By "in any Before Read Logic" do you mean the SQL SELECT can be put in NON PRIMARY file?In theory you can replace any SEL-XXX by a SQL SELECT statement that might return rows or in any Before Read logic, where you might define table keys.
I thought SEL-XXX or SQL SELECT only works in DEFAULT Logic (which means it affect only the primary file).
In fact, I found that SEL-XXX works also in BEFORE logic (which made me confused at the first time when I found this) I do not know if SQL SELECT can be put in BEFORE logic though. (Primary and Secondary file???)
#9
CSuarezdelReal
-
- Members
-
- 91 posts
Advanced
- Gender:Not Telling
Posted 30 September 2004 - 01:22 PM
I use the Default Logic for SQL in primary files. As when you define Table Keys, depending on several aspects, some times they do not work on BEFORE READ logics. I guess it is the same with SQL statements. If defining table keys works in BEFORE READ logic, so should work a SQL select, otherwise, it would be ignored.
Yes, I use often SQL select in BEFORE READ logic for secondary files, and again, that saves a few nestings and gains time.
Yes, I use often SQL select in BEFORE READ logic for secondary files, and again, that saves a few nestings and gains time.
Claudio Suarez del Real "It is not the strongest of the species that survive, nor the most intelligent, but the ones most responsive to change."
#11
CSuarezdelReal
-
- Members
-
- 91 posts
Advanced
- Gender:Not Telling
Posted 30 September 2004 - 09:16 PM
I would summarize my point as follows:
If you are using a RDBMS (Oracle, for instance) ANY request for data MUST BE translated into a SQL SELECT statement (this is the unique interface any application can talk to a RDBMS). If you use (a) SEL-XXX, (
define manually keys or © issue a SQL SELECT in a Default Logic/Before Read Logic, the final result will be a SQL SELECT statement, defined automatically by the ProIV Kernel, or specifically tailored by yourself.
Giving that, I can hardly imagine a case where a SQL SELECT statement adds overhead to a Pro IV function.
If you create the SQL SELECT statement by yourself, it is up to you to make it fit to the referred table, though,
If you are using a RDBMS (Oracle, for instance) ANY request for data MUST BE translated into a SQL SELECT statement (this is the unique interface any application can talk to a RDBMS). If you use (a) SEL-XXX, (
define manually keys or © issue a SQL SELECT in a Default Logic/Before Read Logic, the final result will be a SQL SELECT statement, defined automatically by the ProIV Kernel, or specifically tailored by yourself.Giving that, I can hardly imagine a case where a SQL SELECT statement adds overhead to a Pro IV function.
If you create the SQL SELECT statement by yourself, it is up to you to make it fit to the referred table, though,
Claudio Suarez del Real "It is not the strongest of the species that survive, nor the most intelligent, but the ones most responsive to change."
#13
Guest_Pinoy Ako_*
Guest_Pinoy Ako_*
-
- Guests
Posted 01 October 2004 - 03:50 AM
Hi Siobi,
The internet is a very useful source of information, please use it. ;-)
http://www.1keydata.com/sql/sql.html
Cheers
The internet is a very useful source of information, please use it. ;-)
http://www.1keydata.com/sql/sql.html
Cheers
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
Click the link below to see the new game I'm developing!
