When I try to query off of that new index I get this error:I also tried the prefix ifsinfo..
When I try to query the new indexes I do see them:
Tried to grant access to the INDEX:
If I use the _TAB table name in my SQL that it finds it but now it doesn’t have sufficient priviledges:
Great solution!Is it possible to build the Selections from a hard-coded list instead of an IFS table?For instance we have a lobby with the customer District_Code as a selection. We’ve set up customers with groups of DistrictCodes for a company division, i.e., District Codes of 651, 652, 653, 654, 655, and 656 all belong to Division A. So the users want the selection to be:Division > Division A Division B Division C …...which in turn filter by their list of corresponding District Codes.
Thx, Durette; that fills out my understanding.
The base query will run quicker if you make LEVEL_1_FORECAST the first table in your query and then join your way down the rest of the tables because your WHERE clause is referencing this table. I know that oracle can be smart enough to optimise queries but better to give it a fighting change Apply the same approach to the sub queries i.e. Filter the data from the primary table first if possible then join other tables to it. So in your sub queries SELECT blah from INVOSTAT INNER JOIN CUSTOMER_INFO where <INVOSTAT field filters> INNER JOINS vs LEFT JOINS - INNER is ‘better’ if you know the records will always link and may be slightly faster depending on the structure of your query. Re-writing the query as suggested above took care of the performance issue, along with Durette’s reply:and TRUNC(col.invoice_date, 'MM') = TRUNC(l1f.ms_date, 'MM')Thx, everyone for your input! Many good ideas!
fyi, I was able to design a solution.I created an IAL hard-coding the values I wanted, and then used the above solution to plug it into my Lobby. Thx for the effort on this one!select 'Division A' as DIVISIONfrom DUALUNION ALLselect 'Division B' as DIVISIONfrom DUALUNION ALLselect 'Division C' as DIVISIONfrom DUAL
That worked! Thx very much!
Thx! That worked!Any reason why the time didn’t get calculated/populated for Calc_Wanted_Dated?
thx!
thx- that looks very polished!
thx.fyi, we added the ADDRESS_ID column and it ran successfully w/o errors, and said # rows modified, but when we checked the CustomerInfo screen they did not update.
ok, thx for the info- good to know!
great, thx!
thx, I’ll try those. To clarify, these two dates, 3/9 and 3/30, are sorting as 3/30, 3/9 instead of 3/9, 3/30 because it’s treating these as alphanumeric field type instead of Date.Here’s the DataSource that shows it incorrectly sorted:
thx! I’ll try that...
This worked perfectly! Thanks!!!SELECT to_char(SYSDATE, 'MM/DD')
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.