Solved Mariadb latest version 11.0.2 bugs on sql select data into outfile -now fixed !!

Hi folks

fixed -- see next post in this thread

This version (11.0.2) of MariaDB seem to have some file loading bugs in it.

I can only get data into file directories from '/' e.g /tmp. /tmp1 etc.
If I want to load data into say /home/user/testdir which is the best place for testing this stuff -= permission denied.
all directories have total read/write etc access (test machine).

also if you load data into /tmp -- the query runs ok but there's no file !!!!

3 queries 2 OK data only exists in /tmp1 write permission denied on 3rd - even though it's all 100% read write ik etc.

It works on /tmp1

mystery



on /tmp -- no file even though query is OK



Now IMO software shouldn't issue a message to say that execution is successful as in the first case where there's clearly no output.
Config is OK - and on previous releases it's OK.

Imagine if I'd written a query to load up say 70 large files and then found hours later that there was no data loaded in spite of no error messages.

export via phpmyAdmin exports a Null file.

I'd suggest users test VERY CAREFULLY if they use MariaDB or go back to MySQL which is slower -- but at least it works !!!!!

cheers
jimbo

tested on a "virgin minimal clean debian 12 system"

From windows (I was using canary windows VM just ssh to the server hosting the database. For example



The default output file is /tmp which isn't one you want users writing to some system things also write to that directory -- looking at permissions it has ownership of mysql and group mysql.

create a directory with say /data/tmp.
change ownership to mysql both of /data and /data/tmp
then allow users access via chmod 777 on both /data and /data/tmp

this works perfectly now -- seems you have to explicitly add permissions on each level of subdirectory --- seems security has got a bit excessive and other users might have other ways of doing this.

Anyway for me problem is solved i can make a separate partition for /data keeping mysql /mariadb users only to writing / reading from there.

I'd still like user to be able to create their own subdirectories on /data/tmp and get mysql to work -- i'm sure it can but this is a passable get around fix so I've maked the thing as solved. if the same thing happens on windows install then alter permissions accordingly.

cheers
imbo