At 10:52 AM -0700 9/21/05, Jeff Zucker wrote:
The "My" in "MySQL" is the name of the daughter of one of the
founders (Monty IIRC) and has nothing to do with the English word
"my". But don't let me interrupt your rant :-).
Well, you learn interesting new trivia each day; I can use that one;
t
Bart Lateur wrote:
On Sun, 11 Sep 2005 12:38:07 +0300, Philip Stoev wrote:
* Provide the same interface to Postgresql's parser the way it is being done
for MySQL, and at that time "My" in MyParse will no longer stand for MySQL.
That sounds like the worst idea for a module name ever.
Re: ANNOUNCE:: DBIx::MyParse 0.20
On Sun, 11 Sep 2005 12:38:07 +0300, Philip Stoev wrote:
>* Provide the same interface to Postgresql's parser the way it is being done
>for MySQL, and at that time "My" in MyParse will no longer stand for MySQL.
That sounds like the worst idea fo
On Sun, 11 Sep 2005 12:38:07 +0300, Philip Stoev wrote:
>* Provide the same interface to Postgresql's parser the way it is being done
>for MySQL, and at that time "My" in MyParse will no longer stand for MySQL.
That sounds like the worst idea for a module name ever. It reminds me of
the "My Docum
On Sun, Sep 11, 2005 at 12:38:07PM +0300, Philip Stoev wrote:
> Thanks for all the feedback.
>
> With respect to the name of the module, can anyone please point to specific
> documents describing the module naming policy and namespace regulations? I
> am particularily interested in who is to decid
Thanks for all the feedback.
With respect to the name of the module, can anyone please point to specific
documents describing the module naming policy and namespace regulations? I
am particularily interested in who is to decide the proper name of the
module -- am I free to leave the original name
Tim Bunce wrote:
> I've been saying that someone should do this for years[1],
> so I'm delighted you have.
>
> But it doesn't belong in the DBIx namespace. It's unrelated to the DBI.
>
> MySQL::Parse would be a much more suitable location.
> (or perhaps SQL::MyParse, though I think MySQL::Parse i
I've been saying that someone should do this for years[1],
so I'm delighted you have.
But it doesn't belong in the DBIx namespace. It's unrelated to the DBI.
MySQL::Parse would be a much more suitable location.
(or perhaps SQL::MyParse, though I think MySQL::Parse is best)
In terms of implementa
