I Dont want to use ORM- the option to have exploded sql calls dosn't work when you down load the component it still creates ORM type calls.. I had a hack that I could adjust the sql in a modal to look at another components tables. I now cant do this because of ORM.

Yes, thats true, and I cannot do another way, only few calls are done with ORM because they are too long, complex and repetitive.
Can I ask you why don't you want ORM system ?

Hi Chef, mainly because I now don't know how to make changes to what was once a standard query. I was shown a hack so I could adjust a query to point to another component, which worked brilliant for me. "From a previous Post" . ORM seems to have pretty much taken that option away from me. I'm learning as fast as I can to keep up with the changes, but as a novice programmer I am struggling.


PS; Apart from that little issue ORM works fine..

Can the exploded option simply not use ORM and produce the querry's how they where before ORM. Currently the exploded version seems to still use ORM. Why would we have an option for exploded or ORM if the Exploded still uses ORM?

No, that's not possible to remove ORM call completely.

Cook has always produced its code with some kind of ORM before to call it ORM.
For instance, for the accesses propagations -> it was the function prepareQueryAccesses()
And so on...

For N:m filter, the same, it has NEVER existed without ORM
There is no option for disabling ORM, it is only an option to explode the calls, but yes some calls will still exist with ORM.

Can you give me an example for what you are triing to do ?

Maybe we can help you to recreate the hacked bit?

Yes, is it complicated ?

Can you describe the SQL command you need, please ?
And so, if it is not possible with ORM, maybe I can improve ORM, that would be the best if it is possible and makes sense in terms of reusability