On Wed, 09 Jun 2010 08:07:56 -0000, Toru Maesaka <email address hidden> wrote:
> It turns out that to support ENABLE INDEX syntax, the storage engine
> needs to implement Cursor::enable_indexes() and preferably
> Cursor::disable_indexes(). BlitzDB hasn't implemented these functions
> so I suspect this is what's causing the weird behavior.
>
> I have no prior knowledge on this syntax so until I do more research,
> I will make BlitzDB return HA_ERR_UNSUPPORTED. This way, at least the
> user won't have to panic.
sounds like those methods should have returning HA_ERR_UNSUPPORTED as a
default implementation so that others don't run into this too.
On Wed, 09 Jun 2010 08:07:56 -0000, Toru Maesaka <email address hidden> wrote: :enable_ indexes( ) and preferably :disable_ indexes( ). BlitzDB hasn't implemented these functions
> It turns out that to support ENABLE INDEX syntax, the storage engine
> needs to implement Cursor:
> Cursor:
> so I suspect this is what's causing the weird behavior.
>
> I have no prior knowledge on this syntax so until I do more research,
> I will make BlitzDB return HA_ERR_UNSUPPORTED. This way, at least the
> user won't have to panic.
sounds like those methods should have returning HA_ERR_UNSUPPORTED as a
default implementation so that others don't run into this too.
--
Stewart Smith