Hi Folks,
A new question has risen during the development of our storage engine.
In short the engine is providing a read-only view to the server filesystem.
One can issue (implemented via assisted discovery):
CREATE TABLE etc ENGINE=fsview ROOT=‘/etc’;
Then it’s possible to tell:
SELECT n
well, i'm not a expert , and it's not comment about storage engine plugin,
but i will give one example with information schema plugin, there's
parameters to know what you could optimize with where clausule, maybe this
can help:
http://dev.mysql.com/doc/refman/5.7/en/writing-information-schema-plug
Hi, Otto!
On Feb 04, Otto Kekäläinen wrote:
> 2015-02-04 1:21 GMT+02:00 Sergei Golubchik :
> > I can give you a patch that you apply and run another build in the
> > Launchpad build system. Would that be ok?
>
> Yes, please :)
Try this one:
=== modified file 'mysql-test/mysql-test-run.pl'
--- m
Hi, Andras!
On Feb 06, Andras Szabo wrote:
> SELECT name, fsize FROM etc WHERE path = “init.d”;
>
> However we’re in a bit of trouble how we could improve the storage
> engine to be able to handle this.
>
> Of course we would not like to do a "deep enumeration" of the root
> directory (full tab
Hi, Otto!
On Feb 05, Otto Kekäläinen wrote:
> Hello!
>
> The errors in the build log
> https://reproducible.debian.net/rbuild/mariadb-10.0_10.0.16-1.rbuild.log
> look like this:
>
> /tmp/buildd/mariadb-10.0-10.0.16/storage/connect/ha_connect.cc:174:46:
> error: macro "__DATE__" might prevent rep
5 matches
Mail list logo
