Dean Arnold wrote:
- embedded SQL syntax for various databases - possible feature requests/needs for optimal Perl integration - alternate namespace suggestions
Are you actually going to be parsing SQL, or just looking for "EXEC SQL" and grabbing the SQL and feeding it to the drivers? If you're going to be parsing SQL, let's talk - I'm (slowly) rewriting SQL::Statement in Parse::Yapp and would be glad to collaborate in any way that would be helpful. If you're not going to be parsing SQL (other than to know where the statements begin and end), then I suggest a name more along the lines of SQL::Exec or SQL::Inline.
After some consideration, probably both.
I.e., if its just a std. SQL statement (SELECT, UPDATE, INSERT, DELETE etc), then SQL::Preproc would recognize the intro keyword (required to be uppercase) and parse the SQL. If a platform has some non-std extension, then the EXEC SQL prefix would be required to pick it up.
RE: dbish...yes, you may be right...something for me to ponder on the drive up to Portland...I guess I'm trying to come at perl from the perspective of a 17 year SQL hacker, but relative perl acolyte (well, hopefully more a journeyman now).
Being able to jump into perl to do database stuff by just inserting the SQL statements, knowing a few implicitly defined variables, and a minimal perl syntax for control flow, might be a gentler introduction.
On the other hand, I might just be out of my tiny little mind...
- Dean
