(this thread was taken from 'Baan and new Oracle features' as requested)

Basically what I would like is an option to see how the driver will translate 4GL into Oracle without having to run the code.

In our organization all SQL has to be approved by the DBA group before it is introduced to the system to avoid "dumb" queries causing unnescesary stress.
Baan currently doesn't comply to this policy because there is no way to determine what the eventual code is going to look like and therefore there is no way of telling how the code can be improved before the code is actually ran.

I would like to take the guess-work out of Baan SQL-development.

I hope this explains my suggestion better, but please contact me if you have a need for more details. I for one really appreciate what you are doing here.

Ok, as this becomes a bit more off topic I will discuss this with you private. When it becomes usefull for more people we can drop our conversation in a new thread.

Kind regards,
Dick

Please ask the moderators to split this thread, because "going private" I think will only solve Francesco questions, but more are interrested in how the database driver does parse the offered SQL queries (to be able to write optimal performing queries and to judge the programmers skills in the standard).

Since Francesco is moderator too, he can split the thread.

Indeed optimizing queries is another topic with a lot of spitzfinger gefuhl as both the Baan driver and the database optimizer are improved (or not ;)) every next version. And off course there are still people running Level 1 drivers and also looking for general guidelines.

For Level 2 I have an old document that explains some general guidelines. Hopefully this document is not too old...

For Level 1 it is more complex as all temptations showed lots of exceptions. Maybe when I find some time in the near future I can summarize or collect these guidelines.

Hopefully this what you are looking for.

Kind regards,
Dick