ForceLiterals

vamsi_praneeth
Member Posts: 23
What are actually ForceLiterals and where actually are these used...?? I hope this ain't an alien question...coz my previous question hasn't been answered inspite of 33 visits...Hope this one would and could be answered.
0
Comments
-
hi, I hope this will help youKeyword Options for select Statements Keyword
Description
firstfast
Fetches the first selected record faster than the remaining selected records.
firstonly
Returns only the first selected record.
forupdate
Selects records for updating.
nofetch
Specifies that the Dynamics AX runtime should not execute the statement immediately because the records are required only by some other operation.
forceplaceholders
Forces the Dynamics AX runtime to generate a query with placeholder field constraints. For example, the query generated for the preceding code example looks like this: select * from myTable where myField1=?. Database query plans are reused when this option is specified. This is the default option for select statements that do not join table records. This keyword cannot be used with the forceliterals keyword.
forceliterals
Forces the Dynamics AX runtime to generate a query with the specified field constraints. For example, the query generated for the preceding code example looks like this: select * from myTable where myField1='value'. Database query plans are not reused when this option is specified. This keyword cannot be used with the forceplaceholders keyword.
forceselectorder
Forces the Microsoft SQL Server query processor to access tables in the order in which they are specified in the query. (No effect on Oracle.)
forcenestedloop
Forces the SQL Server query processor to use a nested-loop algorithm for table join operations. Other join algorithms, such as hash-join and merge-join algorithms, are therefore not considered by the query processor.
reverse
Returns records in reverse of the select order.
The following code example demonstrates how a table index clause is used to suggest the index that a database server should use when querying tables. The Dynamics AX runtime appends an order by clause and the index fields to the first select statement's database query. Records are thus ordered by the index. The Dynamics AX runtime inserts an optional query hint into the second select statement's database query.going to Europe0 -
is there an alternative to use "nofetch" while retrieving data from query object and not from select?0
-
And you'd better not to use this future, so it is not work well.going to Europe0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions