My 2 cents. I would address the question with "What is the purpose
of Drizzle?".
Is it a highly pluggable micro-kernel database?
There has been discussion about compatibility with MySQL. While
Drizzle remains a relational database and provides ANSI compliant SQL,
should do we need to continue to push features that could be culled
into the compatibility debate.
Regardless of any MySQL system in use today, some modifications will
be necessary to use Drizzle correct? While we don't want to rewrite
the book, we should accept that migrating to new cleaner ways because
of code simplicity is a great thing and we (as in the community) have
a chance to simplify.
While not being involved in any of the code purge, it has been exactly
that. A purge. I vote for removing SHOW and creating a necessary
command line interface tool as discussed. There has been at least
come comments about being for example to do a SHOW CREATE TABLE syntax
via I_S (especially in 5.0). Perhaps when removing a SHOW command
provides for extreme complexity, that is added into the I_S schema
data.
I'll throw another spanner out there. Why doesn't somebody write
UDFs() for the SHOW commands, like:
SELECT SHOW('databases'); or similar?
Pluggable UDF's are easier to implement in Drizzle, correct? Is this
easier then additional parser work.
I'm not heavily involved in development so I'll defer to the experts
on what is easier v harder, possible or not.
Regards
Ronald
On Mon, Apr 6, 2009 at 4:49 PM, Sheeri K. Cabral <[email protected]> wrote:
> On Mon, Apr 6, 2009 at 3:28 PM, Jay Pipes <[email protected]> wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Brian Aker wrote:
>> > Hi!
>> >
>> > On Apr 6, 2009, at 12:03 PM, Eric Day wrote:
>> >
>> >> Not sure if I agree here. I think a pre-parser plugin/module would
>> >> be better than sticking this in the client library. This way we
>> >
>> > A query rewriter before the parser call would be pretty damn simple...
>>
>> Yeah, but the problem is then we basically make this a required,
>> built-in module for everyone, since this functionality would be required
>> for everyone pretty much....
>
> No, it can be an optional module, that almost everyone (that comes from the
> MySQL world) installs. I'm all for not coming with it by default so people
> have to learn about information_schema. Not everyone will be coming from
> the MySQL world, as well.
>
> -Sheeri
>
> _______________________________________________
> Mailing list: https://launchpad.net/~drizzle-discuss
> Post to : [email protected]
> Unsubscribe : https://launchpad.net/~drizzle-discuss
> More help : https://help.launchpad.net/ListHelp
>
>
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
