There could be some magic feature that would make this time saver feature. :-)
Then we could make a simple query to build the 'skeleton' of a query and then introduce the aditional rules that cannot be defined in a simple query.
Problem solved.
Thanks Hekhuis for your brilliant explanation.
Hi All,
I think the need is still there its not "Problem Solved". Simple example, If you have to write an aggregate to do a search in Database with matching logic for string (for example Janice) with the string has special character (for example Jânice) then it is not been differentiated by outsystems. It just assumes both the string are same and fetch both. To solve this only way is to write advance query with asciistr method to do it and then if the aggregate is having a join of 10 tables its like a nightmare to do the same manually. I still believe its a must need. Also if anyone have any better idea to do this comparison in aggregate itself and provide me a solution will be really amazing.
Thanks.
Hi Bipasha,
Your problem has nothing to do with this Idea. The reason it doesn't differentiate between "Janice" and "Jänice" has to do with the collation settings of the database. Using asciistr is just a crude workaround. But again, nothing to do with conversion of Aggregate to SQL.