drizzle-discuss team mailing list archive
Mailing list archive
Re: libdrizzle releases
I thought your JDBC driver spoke the MySQL protocol as well, does it
not? If so, we can just change the default porti/protocol (what I'm
going in libdrizzle) once the serrver changes have been out for a bit.
I've not fully tested regular MySQL APIs yet, but certain things
will certainly not work. For example, we only spport a small subset
of command types.
On Thu, Nov 12, 2009 at 09:28:29AM +0100, Marcus Eriksson wrote:
> On Thu, Nov 12, 2009 at 12:15 AM, Eric Day <eday@xxxxxxxxxxxx> wrote:
> Hi everyone,
> I wanted to give an update on the original email I sent below. After
> sending this out, it was decided to make backwards compatibility more
> of a priority now, and steps are being taken to not force upgrades
> for any of the releases of Drizzle and libdrizzle.
> First, I've added support for the MySQL protocol back into Drizzle
> and it will start listening on port 3306 along with the Drizzle
> port. We are going to default back to this port/protocol in libdrizzle
> sometime soon and this will temporarily be the default protocol for
> Drizzle. This allows us to keep the Drizzle port free to change and
> experiment on without interrupting other usage.
> Other usage == other libdrizzle based clients i guess? The java people
> will have to change driver. (or atleast reconfigure the current one, might
> work to use jdbc:mysql:thin, but i have not tested)