Konstantin Osipov wrote:
* Jay Pipes [09/07/09 00:02]:
The current aim is to remove things that obviously aren't related to a
cursor and move them up.
e.g. create table is now in StorageEngine.
at some point s/handler/cursor/
Bad idea IMHO. You don't need to keep all cursors in the table cache
* Jay Pipes [09/07/09 00:02]:
>>> The current aim is to remove things that obviously aren't related to a
>>> cursor and move them up.
>>> e.g. create table is now in StorageEngine.
>>> at some point s/handler/cursor/
>> Bad idea IMHO. You don't need to keep all cursors in the table cache
>> and lo
Hi!
Can you explain this a bit more? I can't follow what you mean by your
statement (even as to how it released to the class MySQL branch).
Cheers,
-Brian
On Jul 8, 2009, at 10:47 AM, Konstantin Osipov wrote:
* Stewart Smith [09/07/08 21:16]:
The current aim is to remove things th
Konstantin Osipov wrote:
* Stewart Smith [09/07/08 21:16]:
The current aim is to remove things that obviously aren't related to a
cursor and move them up.
e.g. create table is now in StorageEngine.
at some point s/handler/cursor/
Bad idea IMHO. You don't need to keep all cursors in the tabl
* Stewart Smith [09/07/08 21:16]:
> The current aim is to remove things that obviously aren't related to a
> cursor and move them up.
>
> e.g. create table is now in StorageEngine.
>
> at some point s/handler/cursor/
Bad idea IMHO. You don't need to keep all cursors in the table cache
and look
At file:///home/psergey/dev/mysql-next-fix-subq/
revno: 2819
revision-id: pser...@askmonty.org-20090708174703-dz9uf5b0m6pcvtl6
parent: pser...@askmonty.org-20090708095341-9i08n2r8igulpxzz
committer: Sergey Petrunya
branch nick: mysql-ne
At file:///home/psergey/dev/maria-5.1-table-elim/
revno: 2727
revision-id: pser...@askmonty.org-20090708171038-9nyc3hcg1o7h8635
parent: pser...@askmonty.org-20090630132018-8qwou8bqiq5z1qjg
committer: Sergey Petrunya
branch nick: maria-5
On Wed, Jul 8, 2009 at 4:24 PM, Brian Aker wrote:
> BTW I suspect for Drizzle we will resurrect BDB at some point in the future
> mainly to provide this sort of interface. From talking to Josh Berkus, there
> may be a standard interface out there defined by some committee that could
> also be used
On Wed, Jul 08, 2009 at 06:49:43PM +0400, Konstantin Osipov wrote:
> * Sergei Golubchik [09/07/08 18:12]:
> > it's WL#3288 (created 22 May 2006) for the API and server support and
> > WL#4603 (17 Oct 2008) for the default implementation in the handler
> > class.
>
> Taking the opportunity to remi
On Wed, Jul 08, 2009 at 06:42:30AM -0400, Peter Benjamin Volk wrote:
>
HTML mail isn't a good idea... not as easy to read.
> Multiple things. At first of course at column store oriented engines.
> The problem with this is that the MySQL core is strongly row based and
> would not take any column
Hi!
On Jul 8, 2009, at 7:49 AM, Konstantin Osipov wrote:
3 disparate storage engine APIs in Drizzle, MySQL and MariaDB.
We have 4 :)
The original MySQL one which all of the vendors use. Drizzle, the
MySQL (Sun/Oracle) created one, and the MariaDB one.
Most of the vendors who have ported
* Sergei Golubchik [09/07/08 18:12]:
> it's WL#3288 (created 22 May 2006) for the API and server support and
> WL#4603 (17 Oct 2008) for the default implementation in the handler
> class.
Taking the opportunity to remind that I still need a review
on my patch for 3288 :-).
Stewart, as for Drizz
Hi, Peter!
On Jul 08, Peter Benjamin Volk wrote:
> Hi Stewart,
>
> Stewart Smith wrote:
> > The idea being to move the handler to be a cursor on a table, with
> > actions not pertaining that to reside in StorageEngine (e.g. DDL).
> >
> > So, is there somebody interested in working with me to h
Stewart Smith wrote:
The idea being to move the handler to be a cursor on a table, with
actions not pertaining that to reside in StorageEngine (e.g. DDL).
That sounds like an interesting Idea. This would though involve quite a
few changes. Would the curser then
On Wed, Jul 08, 2009 at 03:53:15AM -0400, Peter Benjamin Volk wrote:
> Stewart Smith wrote:
> > The idea being to move the handler to be a cursor on a table, with
> > actions not pertaining that to reside in StorageEngine (e.g. DDL).
> >
> That sounds like an interesting Idea. This would though
At file:///home/psergey/dev/mysql-next-fix-subq/
revno: 2818
revision-id: pser...@askmonty.org-20090708095341-9i08n2r8igulpxzz
parent: pser...@askmonty.org-20090706143329-72s3e73rov2f5tml
committer: Sergey Petrunya
branch nick: mysql-ne
Hi Stewart,
Stewart Smith wrote:
> The idea being to move the handler to be a cursor on a table, with
> actions not pertaining that to reside in StorageEngine (e.g. DDL).
>
That sounds like an interesting Idea. This would though involve quite a
few changes. Would the curser then still be row ba
So, I've been making a fair bit of changes around bits of the storage
engine API (by all accounts for the better) in Drizzle.
The idea being to move the handler to be a cursor on a table, with
actions not pertaining that to reside in StorageEngine (e.g. DDL).
There's also the (now rather old) cha
I agree with Lenz and Vadim on this one.
The Launchpad bug tracker is not perfect but I find it quite
sufficient. The user interface is easy to use which is important. But,
the greatest advantage is the close integration with the rest of
Launchpad.
On Jul 7, 2009, at 7:31 PM, Vadim Tkache
19 matches
Mail list logo
