On Fri, 1 Mar 2002, Ken Williams wrote: > Date: Fri, 1 Mar 2002 15:51:21 -0600 > From: Ken Williams <[EMAIL PROTECTED]> > To: Ken Y. Clark <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: SQL translator module: DBIx:: or SQL::? > > > On Thursday, February 28, 2002, at 04:10 PM, Tim Bunce wrote: > > > On Thu, Feb 28, 2002 at 03:23:44PM -0500, Ken Y. Clark wrote: > >> Since what I've got isn't really related to > >> DBI[1], I figure it probably more belongs in SQL::. Also, SQL:: is > >> less crowded, so I'm hoping my module wouldn't get lost in the > >> shuffle. Specifically, I was thinking "SQL::Translator" for the > >> package name, with all the rest of my modules (Parsers, Producers, > >> etc.) living under there. > > > > Sounds good to me. > > Agreed, I think SQL::Translator is a decent name. > > A question, though - does this mean you've got some sort of > dialect-independent representation of SQL queries? That's kind of > interesting. Might it be possible to open that interface up, so that > people could write some sort of neutral-SQL and send it to whatever > database they feel like that day? > > > -Ken
Actually, I'm now leaning towards SQL::SchemaTranslator, as that exactly describes what I'm trying to do. I'm only interested in translating a MySQL (or whatever) schema to some other schema (though I also think an XML output could also prove useful). This is as much as I can see realistically accomplishing with my project, and I'm not all the interested in trying what you've suggested (though I think it's a good idea). In my current project, I develop locally on MySQL, but I have to deploy on Oracle. My workaround is not to abstract the SQL to an interface like you suggest, but simply to write queries I know will work on both (and hopefully on just about any other RDBMS). I personally don't like OO or procedural interfaces for SQL generation, but that's just my taste. All that said, I can see leaving the namespace open for someone who'd like to try. I could stay with SQL::Translator::Schema for my stuff, but that sure is a lot of colons. :) I think I'd prefer to stick with SQL::SchemaTranslator. I've already done my first CVS commit on Sourceforge with SQL::Translator, (project name "SQL Fairy," cvs.sqlfairy.sourceforge.net), but I can change that. Anyone interested in what I have so far can checkout the code from SF. If you're interested in becoming a developer on the project, just let me know. I'm still figuring out how to use SF's tools, but I think I've got the basics. ky
