Hi Isomorphic,
I noted that the order of fields in the generated SQL is random (or random looking to the user). I suppose that this is because during parsing of ds.xml-files you internally use some Java collection type not guaranteeing insertion-order when iterating.
If there is no reason for this I'm not seeing right now (speed can't be an issue for these small lists), it might be a good idea to replace the use of java.util.HashSet(?) by java.util.LinkedHashSet(?).
That way one would get a comprehensible SelectClause. The WhereClause is already stable from my feeling.
Besides being comprehensible, the SQL would also be able to profit from (Oracle) Plan Baseline features. I'm not using that (still developing on Oracle XE ;) and don't think that I'll ever use it (especially not with SmartGWT, where the generated SQL and WhereClause tends to differ for every user interaction).
Having said that, this enhancement (for me) is just a purely cosmetic improvement, but for other users (on Oracle Enterprise Edition) this might have some practical use.
What do you think about this?
Best regards,
Blama
I noted that the order of fields in the generated SQL is random (or random looking to the user). I suppose that this is because during parsing of ds.xml-files you internally use some Java collection type not guaranteeing insertion-order when iterating.
If there is no reason for this I'm not seeing right now (speed can't be an issue for these small lists), it might be a good idea to replace the use of java.util.HashSet(?) by java.util.LinkedHashSet(?).
That way one would get a comprehensible SelectClause. The WhereClause is already stable from my feeling.
Besides being comprehensible, the SQL would also be able to profit from (Oracle) Plan Baseline features. I'm not using that (still developing on Oracle XE ;) and don't think that I'll ever use it (especially not with SmartGWT, where the generated SQL and WhereClause tends to differ for every user interaction).
Having said that, this enhancement (for me) is just a purely cosmetic improvement, but for other users (on Oracle Enterprise Edition) this might have some practical use.
What do you think about this?
Best regards,
Blama
Comment