For sure this would greatly help the effort to shorten development cycle, but I have performance concern against the idea to generate SQL statement automatically. (This is more a general concern, not directly against your idea, as I have read all of your replies you posted so far, and know you are not trying to generate all SQL statement on fly.)

My database experience is mainly with ORACLE and reasonablly large database (some of the tables go up to 3 million record, for example, we have a table to hold sales history for 3 months). My experience tells me that, most of the time, your host language would not cause serious performance problems, even if you are not a wizard of your host language. Performance problem is almost always caused by database, and one major source is your SQL statement.

A slight but thoughtful adjustment of your join, or your where clause might make your SQL statement 100 times faster, or even more. And I simply think it would be extreamly difficult to generate SQL statements that have good performance consistantly. And it is surely more difficult to make the performance to be consistant across different databases.

Another source of difficulty is the SQL syntax differences, although the basic is always the same every where. Some of those extensions are for performance.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.