Re: [Maria-developers] [Maria-discuss] Interval in MYsql query

[Peter Laursen]

Use the DATE_ADD( ) or DATE_SUB() function with INTERVAL as explained here:
https://dev.mysql.com/doc/refman/8.0/en/date-and-time-functions.html#function_date-add

-- Peter.

On Wed, May 16, 2018 at 4:07 PM, Dev C  wrote:

> Hello
>
> If I use below query
> (metrics_5.created_at)>'5/10/2018'- 28 )
> it gives me some result
> but if i use below query
> (metrics_5.created_at)>'5/10/2018'- INTERVAL 28 DAY )
>
> It does not give me any result, any one know why ?
>
> ___
> Mailing list: https://launchpad.net/~maria-discuss
> Post to : maria-disc...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~maria-discuss
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Deprecate INT(M) in SHOW?

[Peter Laursen]

I would also disadvise diverging from MySQL here, as the is no particular
reason as far as I can see.

-- Peter

On Mon, Apr 23, 2018 at 4:17 PM, jocelyn fournier <
jocelyn.fourn...@gmail.com> wrote:

>
>
> > Le 23 avr. 2018 à 15:51, Alexander Barkov  a écrit :
> >
> > Does anybody see any problems if in 10.4 we fix all metadata statements,
> > such as:
> >
> > - SHOW CREATE TABLE t1
> > - DESCRIBE t1
> > - SELECT * FROM INFORMATION_SCHEMA.COLUMNS
> > not to print the default length for non-ZEROFILL columns?
> >
>
> Hi Alexander,
>
> The only issue I can see is for existing applications which try to parse
> the output of those statements and are expecting the length in their regex.
> So I'm not sure it's worth changing this output?
>
>   Jocelyn
> ___
> Mailing list: https://launchpad.net/~maria-developers
> Post to : maria-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~maria-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Deprecate INT(M) in SHOW?

[Peter Laursen]

https://dev.mysql.com/doc/refman/8.0/en/numeric-type-overview.html "
*M* indicates
the maximum display width for integer types. The maximum display width is
255. Display width is unrelated to the range of values a type can contain"

I just inserted "11" into an INT(5) column and was able to create a
INT(200) column as well.

On Mon, Apr 23, 2018 at 3:59 PM, Reindl Harald 
wrote:

>
>
> Am 23.04.2018 um 15:51 schrieb Alexander Barkov:
> > Does anybody see any problems if in 10.4 we fix all metadata statements,
> > such as:
> >
> > - SHOW CREATE TABLE t1
> > - DESCRIBE t1
> > - SELECT * FROM INFORMATION_SCHEMA.COLUMNS
> > not to print the default length for non-ZEROFILL columns?
> yes - consumer code may rely on parse outputs
>
> and frankly i assumed that when i define a unsigned tinyit(2) in can
> hold 0-99 and would reject -1 oder 100 in strict-mode with an error
>
> ___
> Mailing list: https://launchpad.net/~maria-developers
> Post to : maria-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~maria-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Wording suggestion?

[Peter Laursen]

or 'concurrent_assign'/'concurrent assignment'

-- Peter

On Tue, Jan 30, 2018 at 11:35 AM, Peter Laursen <peter_laur...@webyog.com>
wrote:

> 'concurrent_eval'/'concurrent_evaluation'
>
> ?'?
>
>
> -- Peter
> -- Webyog
>
> On Mon, Jan 29, 2018 at 6:19 PM, Sergei Golubchik <s...@mariadb.org>
> wrote:
>
>> Hi, Ian, Russell,
>>
>> As you know, UPDATE in MariaDB is executed left-to-right, say, in the
>> case of
>>
>>   UPDATE t1 SET a=b, b=a
>>
>> both columns will have the same value, old value of `b`. We're now
>> introducing a new sql_mode to have standard compatible behavior, where
>> all assignments are executed kind of "simultaneously" (and the statement
>> above would swap the values).
>>
>> What could the name for this new sql_mode be?
>>
>> Regards,
>> Sergei
>>
>> ___
>> Mailing list: https://launchpad.net/~maria-developers
>> Post to : maria-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~maria-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Fwd: Need Help

[Peter Laursen]

"mysqldump --no-data" should do, I believe. Or use a GUI-tool that has the
option to create structure-only dumps. Or do things in one operation
(eliminate the need for an intermediate script) with some "Schema Sync"
tool such as http://sqlyogkb.webyog.com/article/302-schema-synchronization.

-- Peter
-- Webyog

On Thu, Nov 30, 2017 at 2:15 PM, Deepak Gupta 
wrote:

> Hi There,
>
> I am working on a project where I have some wired requirement for my
> project.
>
> Issue : I am looking for the generic script that I can run with the help
> of Admin rights on the data base and I want the return output in such a way
> that it will give me the complete data base structure along with the table
> relation ship.
>
> For an example , there is one HR schema , with in that schema there might
> be 100 tables example , Employee / Salary / Address / Department etc and
> every table has primary and foreign key concept. So I need the script
> should be such a way that it will fetch all these information and as soon
> as I run the same script in my local system it will replicate the same data
> base structure for me in my local system.
>
> Kindly suggest how can I achieve this requirement ? Any help or
> suggestions are more than welcome.
>
> Looking foreword to here you soon.
>
> Thanks D
>
>
> ___
> Mailing list: https://launchpad.net/~maria-developers
> Post to : maria-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~maria-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Why reserved keywords: UTC_TIME, UTC_DATE, UTC_DATETIME

[Peter Laursen]

They are listed as reserved words in MySQL documentation for any version
from 5.0 and up (at least):
https://dev.mysql.com/doc/refman/5.0/en/keywords.html.

I think compablity with MySQL here is an even or a more valid/important
concern here than standards' compliance.
This is actually a minor issue with standards in MySQL ( + derivates ) as
compared to lots of other non-compliances IMO.
If standards should decide there would never have been MySQL!

Anyway it is not a big deal whether ON or OFF, I think.

But maybe the parser require them as reserved for some casesdue to
imperfections in the parser itself?  This could be why they were made
reserved.
That sould at least be checked carefully before changing anything.

-- Peter
-- Webyog

On Sun, Apr 24, 2016 at 1:13 PM, Alexander Barkov  wrote:

> Hello,
>
> I noticed that UTC_TIME, UTC_DATE, UTC_DATETIME are reserved keywords:
>
>
> MariaDB [test]> SELECT * FROM utc_time;
> ERROR 1064 (42000): You have an error in your SQL syntax; check the manual
> that corresponds to your MariaDB server version for the right syntax to use
> near 'utc_time' at line 1
>
>
> I think they should not.
>
> - These keywords are not mentioned in the SQL standard
> - They are not involved in any complex grammar that would prevent them
>   from being non-reserved keywords
>
> Looks like a bug...
>
> Any objections to make them non-reserved keywords in 10.2?
>
> ___
> Mailing list: https://launchpad.net/~maria-developers
> Post to : maria-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~maria-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Virtual columns and 'mysqldump' (and similar)

[Peter Laursen]

NOTHING is inserted to the Virtual Column. The value specified for it is
ignored.  That is the point!

-- Peter

On Mon, Nov 9, 2015 at 11:10 AM, Peter Laursen <peter_laur...@webyog.com>
wrote:

> I posted this blog:
> http://blog.webyog.com/2015/11/09/beware-virtual-columns-may-render-backups-unusable/.
> It should appear on planet.mysql.com shortly.
>
> -- Peter
>
> On Mon, Nov 9, 2015 at 10:17 AM, Peter Laursen <peter_laur...@webyog.com>
> wrote:
>
>> YES .. it is sql_mode that makes the difference as I realized Friday
>> night here..
>>
>>
>>
>> CREATE TABLE `vc_test`.`t1`(
>>   `id` INT NOT NULL,
>>   `id3` INT AS ( id*3 ) VIRTUAL
>> );
>> SET sql_mode = 'strict_all_tables';
>> INSERT INTO `vc_test`.`t1` VALUES (1,3);
>> -- returns: Error Code: 1906 - The value specified for computed column
>> 'id3' in table 't1' ignored
>> SELECT * FROM t1;
>> -- returns empty set
>>
>> SET sql_mode = '';
>> INSERT INTO `vc_test`.`t1` VALUES (1,3); -- success
>> SHOW WARNINGS;
>> -- 1906  The value specified for computed column 'id3' in table 't1'
>> ignored
>>
>> SELECT * FROM t1;
>> -- returns data
>>
>>
>>
>> Is this intentional or an oversight? Either the INSERT should be allowed
>> in strict mode as well or the error message should be changed. Right?
>>
>>
>> -- Peter
>>
>> On Sat, Nov 7, 2015 at 8:28 AM, Peter Laursen <peter_laur...@webyog.com>
>> wrote:
>>
>>> Stupid oversight on my side: it probably depends on sql-mode. I will
>>> check on Monday.
>>>
>>> But if this is desired behavior (what I don't think) then at least the
>>> error message is wrong and confusing in strict mode.
>>>
>>> -- Peter
>>>
>>> On Fri, Nov 6, 2015 at 10:53 AM, Peter Laursen <peter_laur...@webyog.com
>>> > wrote:
>>>
>>>> There are updates in the bug report (
>>>> http://bugs.mysql.com/bug.php?id=79148).  Those who are interested in
>>>> the subject should read it.
>>>>
>>>> Unfortunately Oracle chose a client-side and not server-side solution
>>>> to this problem. As a consequence 'mysqldumps' from Oracle/MySQL will
>>>> restore in MariaDB, but not vice versa. And dumps generated by (probably)
>>>> all other clients than mysqldump will now fail to restore on Oracle/MySQL
>>>> if table has virtual columns.
>>>>
>>>> I also would be surprised if replication between a MySQL and MariaDB
>>>> server is not affected in some scenarios.
>>>>
>>>> This is at least what I can understand.
>>>>
>>>> -- Peter
>>>>
>>>> On Fri, Nov 6, 2015 at 1:41 PM, Peter Laursen <peter_laur...@webyog.com
>>>> > wrote:
>>>>
>>>>> Further research:
>>>>>
>>>>>
>>>>>
>>>>> It *does not work* with the .msi package for Windows:
>>>>>
>>>>>
>>>>> select version();
>>>>> -- 10.1.8-MariaDB
>>>>>
>>>>> CREATE TABLE `t1_virtual_uk` (
>>>>>   `f1` int(11) DEFAULT NULL,
>>>>>   `gc` int(11) AS (f1 + 1) VIRTUAL
>>>>> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
>>>>>
>>>>> insert into `t1_virtual_uk` values (1,2);
>>>>> -- Error Code: 1906 The value specified for computed column 'gc' in
>>>>> table 't1_virtual_uk' ignored
>>>>>
>>>>> select * from `test`.`t1_virtual_uk`;
>>>>> -- empty set
>>>>>
>>>>>
>>>>> It *does work* on Windows using the .zip package (simply starting
>>>>> server with"mysqld --port = "), however.
>>>>>
>>>>>
>>>>> So the problem seems to be a packaging issue with the .msi. Some
>>>>> old/wrong code seems to go in there.
>>>>>
>>>>>
>>>>> -- Peter
>>>>>
>>>>> On Fri, Nov 6, 2015 at 12:21 PM, Peter Laursen <
>>>>> peter_laur...@webyog.com> wrote:
>>>>>
>>>>>> Correction .. there is no error (except for my copy-paste error).
>>>>>> This is perfect and exactly as I think it should be.
>>>>>>
>>>>>>
>>>>>>
>>>>>> SELECT VERSION(); -- 10.1.8-MariaDB
>>>>>>
>>>>>> CREA

Re: [Maria-developers] Virtual columns and 'mysqldump' (and similar)

[Peter Laursen]

YES .. it is sql_mode that makes the difference as I realized Friday night
here..



CREATE TABLE `vc_test`.`t1`(
  `id` INT NOT NULL,
  `id3` INT AS ( id*3 ) VIRTUAL
);
SET sql_mode = 'strict_all_tables';
INSERT INTO `vc_test`.`t1` VALUES (1,3);
-- returns: Error Code: 1906 - The value specified for computed column
'id3' in table 't1' ignored
SELECT * FROM t1;
-- returns empty set

SET sql_mode = '';
INSERT INTO `vc_test`.`t1` VALUES (1,3); -- success
SHOW WARNINGS;
-- 1906  The value specified for computed column 'id3' in table 't1'
ignored

SELECT * FROM t1;
-- returns data



Is this intentional or an oversight? Either the INSERT should be allowed in
strict mode as well or the error message should be changed. Right?


-- Peter

On Sat, Nov 7, 2015 at 8:28 AM, Peter Laursen <peter_laur...@webyog.com>
wrote:

> Stupid oversight on my side: it probably depends on sql-mode. I will check
> on Monday.
>
> But if this is desired behavior (what I don't think) then at least the
> error message is wrong and confusing in strict mode.
>
> -- Peter
>
> On Fri, Nov 6, 2015 at 10:53 AM, Peter Laursen <peter_laur...@webyog.com>
> wrote:
>
>> There are updates in the bug report (
>> http://bugs.mysql.com/bug.php?id=79148).  Those who are interested in
>> the subject should read it.
>>
>> Unfortunately Oracle chose a client-side and not server-side solution to
>> this problem. As a consequence 'mysqldumps' from Oracle/MySQL will restore
>> in MariaDB, but not vice versa. And dumps generated by (probably) all other
>> clients than mysqldump will now fail to restore on Oracle/MySQL if table
>> has virtual columns.
>>
>> I also would be surprised if replication between a MySQL and MariaDB
>> server is not affected in some scenarios.
>>
>> This is at least what I can understand.
>>
>> -- Peter
>>
>> On Fri, Nov 6, 2015 at 1:41 PM, Peter Laursen <peter_laur...@webyog.com>
>> wrote:
>>
>>> Further research:
>>>
>>>
>>>
>>> It *does not work* with the .msi package for Windows:
>>>
>>>
>>> select version();
>>> -- 10.1.8-MariaDB
>>>
>>> CREATE TABLE `t1_virtual_uk` (
>>>   `f1` int(11) DEFAULT NULL,
>>>   `gc` int(11) AS (f1 + 1) VIRTUAL
>>> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
>>>
>>> insert into `t1_virtual_uk` values (1,2);
>>> -- Error Code: 1906 The value specified for computed column 'gc' in
>>> table 't1_virtual_uk' ignored
>>>
>>> select * from `test`.`t1_virtual_uk`;
>>> -- empty set
>>>
>>>
>>> It *does work* on Windows using the .zip package (simply starting
>>> server with"mysqld --port = "), however.
>>>
>>>
>>> So the problem seems to be a packaging issue with the .msi. Some
>>> old/wrong code seems to go in there.
>>>
>>>
>>> -- Peter
>>>
>>> On Fri, Nov 6, 2015 at 12:21 PM, Peter Laursen <peter_laur...@webyog.com
>>> > wrote:
>>>
>>>> Correction .. there is no error (except for my copy-paste error). This
>>>> is perfect and exactly as I think it should be.
>>>>
>>>>
>>>>
>>>> SELECT VERSION(); -- 10.1.8-MariaDB
>>>>
>>>> CREATE DATABASE vctest;
>>>> USE vctest;
>>>>
>>>> CREATE TABLE `t1`(
>>>>   `id` INT NOT NULL,
>>>>   `id3` INT AS ( id*3 ) VIRTUAL
>>>> );
>>>>
>>>> INSERT INTO `t1` VALUES (1,3);
>>>>
>>>> SHOW WARNINGS;
>>>> -- 1906  The value specified for computed column 'id3' in table 't1'
>>>> ignored
>>>>
>>>> SELECT * FROM t1;
>>>> /*
>>>> id id3
>>>> --  
>>>>  1 3
>>>> */
>>>>
>>>> On Fri, Nov 6, 2015 at 12:10 PM, Peter Laursen <
>>>> peter_laur...@webyog.com> wrote:
>>>>
>>>>> yup .. this is good!
>>>>>
>>>>> SELECT VERSION(); -- 10.1.8-MariaDB
>>>>>
>>>>> CREATE DATABASE vctest;
>>>>> USE vctest;
>>>>>
>>>>> CREATE TABLE `t1`(
>>>>>   `id` INT NOT NULL,
>>>>>   `id3` INT AS ( id*3 ) VIRTUAL
>>>>> );
>>>>>
>>>>> INSERT INTO `t1` VALUES (1,3);
>>>>> -- retruns: Error Code: 1906 - The value specified for computed column
>>>>> 'id3' in table 't1' ign

Re: [Maria-developers] Virtual columns and 'mysqldump' (and similar)

[Peter Laursen]

I posted this blog:
http://blog.webyog.com/2015/11/09/beware-virtual-columns-may-render-backups-unusable/.
It should appear on planet.mysql.com shortly.

-- Peter

On Mon, Nov 9, 2015 at 10:17 AM, Peter Laursen <peter_laur...@webyog.com>
wrote:

> YES .. it is sql_mode that makes the difference as I realized Friday night
> here..
>
>
>
> CREATE TABLE `vc_test`.`t1`(
>   `id` INT NOT NULL,
>   `id3` INT AS ( id*3 ) VIRTUAL
> );
> SET sql_mode = 'strict_all_tables';
> INSERT INTO `vc_test`.`t1` VALUES (1,3);
> -- returns: Error Code: 1906 - The value specified for computed column
> 'id3' in table 't1' ignored
> SELECT * FROM t1;
> -- returns empty set
>
> SET sql_mode = '';
> INSERT INTO `vc_test`.`t1` VALUES (1,3); -- success
> SHOW WARNINGS;
> -- 1906  The value specified for computed column 'id3' in table 't1'
> ignored
>
> SELECT * FROM t1;
> -- returns data
>
>
>
> Is this intentional or an oversight? Either the INSERT should be allowed
> in strict mode as well or the error message should be changed. Right?
>
>
> -- Peter
>
> On Sat, Nov 7, 2015 at 8:28 AM, Peter Laursen <peter_laur...@webyog.com>
> wrote:
>
>> Stupid oversight on my side: it probably depends on sql-mode. I will
>> check on Monday.
>>
>> But if this is desired behavior (what I don't think) then at least the
>> error message is wrong and confusing in strict mode.
>>
>> -- Peter
>>
>> On Fri, Nov 6, 2015 at 10:53 AM, Peter Laursen <peter_laur...@webyog.com>
>> wrote:
>>
>>> There are updates in the bug report (
>>> http://bugs.mysql.com/bug.php?id=79148).  Those who are interested in
>>> the subject should read it.
>>>
>>> Unfortunately Oracle chose a client-side and not server-side solution to
>>> this problem. As a consequence 'mysqldumps' from Oracle/MySQL will restore
>>> in MariaDB, but not vice versa. And dumps generated by (probably) all other
>>> clients than mysqldump will now fail to restore on Oracle/MySQL if table
>>> has virtual columns.
>>>
>>> I also would be surprised if replication between a MySQL and MariaDB
>>> server is not affected in some scenarios.
>>>
>>> This is at least what I can understand.
>>>
>>> -- Peter
>>>
>>> On Fri, Nov 6, 2015 at 1:41 PM, Peter Laursen <peter_laur...@webyog.com>
>>> wrote:
>>>
>>>> Further research:
>>>>
>>>>
>>>>
>>>> It *does not work* with the .msi package for Windows:
>>>>
>>>>
>>>> select version();
>>>> -- 10.1.8-MariaDB
>>>>
>>>> CREATE TABLE `t1_virtual_uk` (
>>>>   `f1` int(11) DEFAULT NULL,
>>>>   `gc` int(11) AS (f1 + 1) VIRTUAL
>>>> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
>>>>
>>>> insert into `t1_virtual_uk` values (1,2);
>>>> -- Error Code: 1906 The value specified for computed column 'gc' in
>>>> table 't1_virtual_uk' ignored
>>>>
>>>> select * from `test`.`t1_virtual_uk`;
>>>> -- empty set
>>>>
>>>>
>>>> It *does work* on Windows using the .zip package (simply starting
>>>> server with"mysqld --port = "), however.
>>>>
>>>>
>>>> So the problem seems to be a packaging issue with the .msi. Some
>>>> old/wrong code seems to go in there.
>>>>
>>>>
>>>> -- Peter
>>>>
>>>> On Fri, Nov 6, 2015 at 12:21 PM, Peter Laursen <
>>>> peter_laur...@webyog.com> wrote:
>>>>
>>>>> Correction .. there is no error (except for my copy-paste error). This
>>>>> is perfect and exactly as I think it should be.
>>>>>
>>>>>
>>>>>
>>>>> SELECT VERSION(); -- 10.1.8-MariaDB
>>>>>
>>>>> CREATE DATABASE vctest;
>>>>> USE vctest;
>>>>>
>>>>> CREATE TABLE `t1`(
>>>>>   `id` INT NOT NULL,
>>>>>   `id3` INT AS ( id*3 ) VIRTUAL
>>>>> );
>>>>>
>>>>> INSERT INTO `t1` VALUES (1,3);
>>>>>
>>>>> SHOW WARNINGS;
>>>>> -- 1906  The value specified for computed column 'id3' in table 't1'
>>>>> ignored
>>>>>
>>>>> SELECT * FROM t1;
>>>>> /*
>>>>> id id3
>>>>> --  
>>>>>  1 3
>>&g

Re: [Maria-developers] Virtual columns and 'mysqldump' (and similar)

[Peter Laursen]

Stupid oversight on my side: it probably depends on sql-mode. I will check
on Monday.

But if this is desired behavior (what I don't think) then at least the
error message is wrong and confusing in strict mode.

-- Peter

On Fri, Nov 6, 2015 at 10:53 AM, Peter Laursen <peter_laur...@webyog.com>
wrote:

> There are updates in the bug report (
> http://bugs.mysql.com/bug.php?id=79148).  Those who are interested in the
> subject should read it.
>
> Unfortunately Oracle chose a client-side and not server-side solution to
> this problem. As a consequence 'mysqldumps' from Oracle/MySQL will restore
> in MariaDB, but not vice versa. And dumps generated by (probably) all other
> clients than mysqldump will now fail to restore on Oracle/MySQL if table
> has virtual columns.
>
> I also would be surprised if replication between a MySQL and MariaDB
> server is not affected in some scenarios.
>
> This is at least what I can understand.
>
> -- Peter
>
> On Fri, Nov 6, 2015 at 1:41 PM, Peter Laursen <peter_laur...@webyog.com>
> wrote:
>
>> Further research:
>>
>>
>>
>> It *does not work* with the .msi package for Windows:
>>
>>
>> select version();
>> -- 10.1.8-MariaDB
>>
>> CREATE TABLE `t1_virtual_uk` (
>>   `f1` int(11) DEFAULT NULL,
>>   `gc` int(11) AS (f1 + 1) VIRTUAL
>> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
>>
>> insert into `t1_virtual_uk` values (1,2);
>> -- Error Code: 1906 The value specified for computed column 'gc' in table
>> 't1_virtual_uk' ignored
>>
>> select * from `test`.`t1_virtual_uk`;
>> -- empty set
>>
>>
>> It *does work* on Windows using the .zip package (simply starting server
>> with"mysqld --port = "), however.
>>
>>
>> So the problem seems to be a packaging issue with the .msi. Some
>> old/wrong code seems to go in there.
>>
>>
>> -- Peter
>>
>> On Fri, Nov 6, 2015 at 12:21 PM, Peter Laursen <peter_laur...@webyog.com>
>> wrote:
>>
>>> Correction .. there is no error (except for my copy-paste error). This
>>> is perfect and exactly as I think it should be.
>>>
>>>
>>>
>>> SELECT VERSION(); -- 10.1.8-MariaDB
>>>
>>> CREATE DATABASE vctest;
>>> USE vctest;
>>>
>>> CREATE TABLE `t1`(
>>>   `id` INT NOT NULL,
>>>   `id3` INT AS ( id*3 ) VIRTUAL
>>> );
>>>
>>> INSERT INTO `t1` VALUES (1,3);
>>>
>>> SHOW WARNINGS;
>>> -- 1906  The value specified for computed column 'id3' in table 't1'
>>> ignored
>>>
>>> SELECT * FROM t1;
>>> /*
>>> id id3
>>> --  
>>>  1 3
>>> */
>>>
>>> On Fri, Nov 6, 2015 at 12:10 PM, Peter Laursen <peter_laur...@webyog.com
>>> > wrote:
>>>
>>>> yup .. this is good!
>>>>
>>>> SELECT VERSION(); -- 10.1.8-MariaDB
>>>>
>>>> CREATE DATABASE vctest;
>>>> USE vctest;
>>>>
>>>> CREATE TABLE `t1`(
>>>>   `id` INT NOT NULL,
>>>>   `id3` INT AS ( id*3 ) VIRTUAL
>>>> );
>>>>
>>>> INSERT INTO `t1` VALUES (1,3);
>>>> -- retruns: Error Code: 1906 - The value specified for computed column
>>>> 'id3' in table 't1' ignored
>>>>
>>>> SHOW WARNINGS;
>>>> -- 1906  The value specified for computed column 'id3' in table 't1'
>>>> ignored
>>>>
>>>> SELECT * FROM t1;
>>>> /*
>>>> id id3
>>>> --  
>>>>  1 3
>>>> */
>>>>
>>>> On Fri, Nov 6, 2015 at 11:52 AM, Ian Gilfillan <i...@mariadb.org> wrote:
>>>>
>>>>> The insert statement returns a warning:
>>>>>
>>>>> INSERT INTO `test`.`t1` VALUES (1,3);
>>>>> Query OK, 1 row affected, 1 warning (0.07 sec)
>>>>>
>>>>> Warning (Code 1906): The value specified for computed column 'id3' in
>>>>> table 't1' ignored
>>>>>
>>>>>
>>>>>
>>>>> On 06/11/2015 08:09, Peter Laursen wrote:
>>>>>
>>>>> OK, I should have upgraded. But I am currently travelling an with a
>>>>> small laptop only and an Internet connectivity not fit for downloads (call
>>>>> it a bad excuse if you want! :-) )
>>>>>
>>>>> So it actually INSERTS. That is ni

Re: [Maria-developers] Virtual columns and 'mysqldump' (and similar)

[Peter Laursen]

Further research:



It *does not work* with the .msi package for Windows:


select version();
-- 10.1.8-MariaDB

CREATE TABLE `t1_virtual_uk` (
  `f1` int(11) DEFAULT NULL,
  `gc` int(11) AS (f1 + 1) VIRTUAL
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

insert into `t1_virtual_uk` values (1,2);
-- Error Code: 1906 The value specified for computed column 'gc' in table
't1_virtual_uk' ignored

select * from `test`.`t1_virtual_uk`;
-- empty set


It *does work* on Windows using the .zip package (simply starting server
with"mysqld --port = "), however.


So the problem seems to be a packaging issue with the .msi. Some old/wrong
code seems to go in there.


-- Peter

On Fri, Nov 6, 2015 at 12:21 PM, Peter Laursen <peter_laur...@webyog.com>
wrote:

> Correction .. there is no error (except for my copy-paste error). This is
> perfect and exactly as I think it should be.
>
>
>
> SELECT VERSION(); -- 10.1.8-MariaDB
>
> CREATE DATABASE vctest;
> USE vctest;
>
> CREATE TABLE `t1`(
>   `id` INT NOT NULL,
>   `id3` INT AS ( id*3 ) VIRTUAL
> );
>
> INSERT INTO `t1` VALUES (1,3);
>
> SHOW WARNINGS;
> -- 1906  The value specified for computed column 'id3' in table 't1'
> ignored
>
> SELECT * FROM t1;
> /*
> id id3
> --  
>  1 3
> */
>
> On Fri, Nov 6, 2015 at 12:10 PM, Peter Laursen <peter_laur...@webyog.com>
> wrote:
>
>> yup .. this is good!
>>
>> SELECT VERSION(); -- 10.1.8-MariaDB
>>
>> CREATE DATABASE vctest;
>> USE vctest;
>>
>> CREATE TABLE `t1`(
>>   `id` INT NOT NULL,
>>   `id3` INT AS ( id*3 ) VIRTUAL
>> );
>>
>> INSERT INTO `t1` VALUES (1,3);
>> -- retruns: Error Code: 1906 - The value specified for computed column
>> 'id3' in table 't1' ignored
>>
>> SHOW WARNINGS;
>> -- 1906  The value specified for computed column 'id3' in table 't1'
>> ignored
>>
>> SELECT * FROM t1;
>> /*
>> id id3
>> --  
>>  1 3
>> */
>>
>> On Fri, Nov 6, 2015 at 11:52 AM, Ian Gilfillan <i...@mariadb.org> wrote:
>>
>>> The insert statement returns a warning:
>>>
>>> INSERT INTO `test`.`t1` VALUES (1,3);
>>> Query OK, 1 row affected, 1 warning (0.07 sec)
>>>
>>> Warning (Code 1906): The value specified for computed column 'id3' in
>>> table 't1' ignored
>>>
>>>
>>>
>>> On 06/11/2015 08:09, Peter Laursen wrote:
>>>
>>> OK, I should have upgraded. But I am currently travelling an with a
>>> small laptop only and an Internet connectivity not fit for downloads (call
>>> it a bad excuse if you want! :-) )
>>>
>>> So it actually INSERTS. That is nice. But does it return an error or
>>> warning or nothing? It should not be an error IMO as various clients would
>>> 'abort on error' and flood its log with error messages.
>>>
>>> -- Peter
>>>
>>> On Fri, Nov 6, 2015 at 11:32 AM, Ian Gilfillan <i...@mariadb.org> wrote:
>>>
>>>>
>>>> 06/11/2015 07:51, Peter Laursen wrote:
>>>>
>>>>> I reported this bug report to Oracle:
>>>>> <http://bugs.mysql.com/bug.php?id=79148>
>>>>> http://bugs.mysql.com/bug.php?id=79148
>>>>>
>>>>> It is almost the same in MariaDB - but the error message is different,
>>>>> see
>>>>>
>>>>> SELECT VERSION(); -- 10.1.2-MariaDB-log
>>>>>
>>>>> CREATE TABLE `vc_test`.`t1`(
>>>>>   `id` INT NOT NULL,
>>>>>   `id3` INT AS ( id*3 ) VIRTUAL
>>>>> );
>>>>>
>>>>> INSERT INTO `vc_test`.`t1` VALUES (1,3);
>>>>> -- retruns: Error Code: 1906 - The value specified for computed column
>>>>> 'id3' in table 't1' ignored
>>>>>
>>>>> SELECT * FROM t1;
>>>>> -- returns empty set
>>>>>
>>>>>
>>>>> So here the error message is that "value is ignored" (not that it is
>>>>> "not allowed").  It looks to me like somebody in MariaDB actually
>>>>> identified the problem, but forgot to finish things.
>>>>>
>>>>> The statement should succeed (maybe raise a warning), and the
>>>>> "specified value should be ignored" as the error message says, but what it
>>>>> in reality is not.
>>>>>
>>>>> What say?
>>>>>
>>>>
>>>> In 10.1.8, the above returns:
>>>> SELECT * FROM t1;
>>>> ++--+
>>>> | id | id3  |
>>>> ++--+
>>>> |  1 |3 |
>>>> ++--+
>>>>
>>>>
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~maria-developers
>>> Post to : maria-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~maria-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Virtual columns and 'mysqldump' (and similar)

[Peter Laursen]

There are updates in the bug report (http://bugs.mysql.com/bug.php?id=79148).
Those who are interested in the subject should read it.

Unfortunately Oracle chose a client-side and not server-side solution to
this problem. As a consequence 'mysqldumps' from Oracle/MySQL will restore
in MariaDB, but not vice versa. And dumps generated by (probably) all other
clients than mysqldump will now fail to restore on Oracle/MySQL if table
has virtual columns.

I also would be surprised if replication between a MySQL and MariaDB server
is not affected in some scenarios.

This is at least what I can understand.

-- Peter

On Fri, Nov 6, 2015 at 1:41 PM, Peter Laursen <peter_laur...@webyog.com>
wrote:

> Further research:
>
>
>
> It *does not work* with the .msi package for Windows:
>
>
> select version();
> -- 10.1.8-MariaDB
>
> CREATE TABLE `t1_virtual_uk` (
>   `f1` int(11) DEFAULT NULL,
>   `gc` int(11) AS (f1 + 1) VIRTUAL
> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
>
> insert into `t1_virtual_uk` values (1,2);
> -- Error Code: 1906 The value specified for computed column 'gc' in table
> 't1_virtual_uk' ignored
>
> select * from `test`.`t1_virtual_uk`;
> -- empty set
>
>
> It *does work* on Windows using the .zip package (simply starting server
> with"mysqld --port = "), however.
>
>
> So the problem seems to be a packaging issue with the .msi. Some old/wrong
> code seems to go in there.
>
>
> -- Peter
>
> On Fri, Nov 6, 2015 at 12:21 PM, Peter Laursen <peter_laur...@webyog.com>
> wrote:
>
>> Correction .. there is no error (except for my copy-paste error). This is
>> perfect and exactly as I think it should be.
>>
>>
>>
>> SELECT VERSION(); -- 10.1.8-MariaDB
>>
>> CREATE DATABASE vctest;
>> USE vctest;
>>
>> CREATE TABLE `t1`(
>>   `id` INT NOT NULL,
>>   `id3` INT AS ( id*3 ) VIRTUAL
>> );
>>
>> INSERT INTO `t1` VALUES (1,3);
>>
>> SHOW WARNINGS;
>> -- 1906  The value specified for computed column 'id3' in table 't1'
>> ignored
>>
>> SELECT * FROM t1;
>> /*
>> id id3
>> --  
>>  1 3
>> */
>>
>> On Fri, Nov 6, 2015 at 12:10 PM, Peter Laursen <peter_laur...@webyog.com>
>> wrote:
>>
>>> yup .. this is good!
>>>
>>> SELECT VERSION(); -- 10.1.8-MariaDB
>>>
>>> CREATE DATABASE vctest;
>>> USE vctest;
>>>
>>> CREATE TABLE `t1`(
>>>   `id` INT NOT NULL,
>>>   `id3` INT AS ( id*3 ) VIRTUAL
>>> );
>>>
>>> INSERT INTO `t1` VALUES (1,3);
>>> -- retruns: Error Code: 1906 - The value specified for computed column
>>> 'id3' in table 't1' ignored
>>>
>>> SHOW WARNINGS;
>>> -- 1906  The value specified for computed column 'id3' in table 't1'
>>> ignored
>>>
>>> SELECT * FROM t1;
>>> /*
>>> id id3
>>> --  
>>>  1 3
>>> */
>>>
>>> On Fri, Nov 6, 2015 at 11:52 AM, Ian Gilfillan <i...@mariadb.org> wrote:
>>>
>>>> The insert statement returns a warning:
>>>>
>>>> INSERT INTO `test`.`t1` VALUES (1,3);
>>>> Query OK, 1 row affected, 1 warning (0.07 sec)
>>>>
>>>> Warning (Code 1906): The value specified for computed column 'id3' in
>>>> table 't1' ignored
>>>>
>>>>
>>>>
>>>> On 06/11/2015 08:09, Peter Laursen wrote:
>>>>
>>>> OK, I should have upgraded. But I am currently travelling an with a
>>>> small laptop only and an Internet connectivity not fit for downloads (call
>>>> it a bad excuse if you want! :-) )
>>>>
>>>> So it actually INSERTS. That is nice. But does it return an error or
>>>> warning or nothing? It should not be an error IMO as various clients would
>>>> 'abort on error' and flood its log with error messages.
>>>>
>>>> -- Peter
>>>>
>>>> On Fri, Nov 6, 2015 at 11:32 AM, Ian Gilfillan <i...@mariadb.org> wrote:
>>>>
>>>>>
>>>>> 06/11/2015 07:51, Peter Laursen wrote:
>>>>>
>>>>>> I reported this bug report to Oracle:
>>>>>> <http://bugs.mysql.com/bug.php?id=79148>
>>>>>> http://bugs.mysql.com/bug.php?id=79148
>>>>>>
>>>>>> It is almost the same in MariaDB - but the error 

[Maria-developers] Virtual columns and 'mysqldump' (and similar)

[Peter Laursen]

I reported this bug report to Oracle: http://bugs.mysql.com/bug.php?id=79148

It is almost the same in MariaDB - but the error message is different, see

SELECT VERSION(); -- 10.1.2-MariaDB-log

CREATE TABLE `vc_test`.`t1`(
  `id` INT NOT NULL,
  `id3` INT AS ( id*3 ) VIRTUAL
);

INSERT INTO `vc_test`.`t1` VALUES (1,3);
-- retruns: Error Code: 1906 - The value specified for computed column
'id3' in table 't1' ignored

SELECT * FROM t1;
-- returns empty set


So here the error message is that "value is ignored" (not that it is "not
allowed").  It looks to me like somebody in MariaDB actually identified the
problem, but forgot to finish things.

The statement should succeed (maybe raise a warning), and the "specified
value should be ignored" as the error message says, but what it in reality
is not.

What say?
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Virtual columns and 'mysqldump' (and similar)

[Peter Laursen]

Correction .. there is no error (except for my copy-paste error). This is
perfect and exactly as I think it should be.



SELECT VERSION(); -- 10.1.8-MariaDB

CREATE DATABASE vctest;
USE vctest;

CREATE TABLE `t1`(
  `id` INT NOT NULL,
  `id3` INT AS ( id*3 ) VIRTUAL
);

INSERT INTO `t1` VALUES (1,3);

SHOW WARNINGS;
-- 1906  The value specified for computed column 'id3' in table 't1' ignored

SELECT * FROM t1;
/*
id id3
--  
 1 3
*/

On Fri, Nov 6, 2015 at 12:10 PM, Peter Laursen <peter_laur...@webyog.com>
wrote:

> yup .. this is good!
>
> SELECT VERSION(); -- 10.1.8-MariaDB
>
> CREATE DATABASE vctest;
> USE vctest;
>
> CREATE TABLE `t1`(
>   `id` INT NOT NULL,
>   `id3` INT AS ( id*3 ) VIRTUAL
> );
>
> INSERT INTO `t1` VALUES (1,3);
> -- retruns: Error Code: 1906 - The value specified for computed column
> 'id3' in table 't1' ignored
>
> SHOW WARNINGS;
> -- 1906  The value specified for computed column 'id3' in table 't1'
> ignored
>
> SELECT * FROM t1;
> /*
> id id3
> --  
>  1 3
> */
>
> On Fri, Nov 6, 2015 at 11:52 AM, Ian Gilfillan <i...@mariadb.org> wrote:
>
>> The insert statement returns a warning:
>>
>> INSERT INTO `test`.`t1` VALUES (1,3);
>> Query OK, 1 row affected, 1 warning (0.07 sec)
>>
>> Warning (Code 1906): The value specified for computed column 'id3' in
>> table 't1' ignored
>>
>>
>>
>> On 06/11/2015 08:09, Peter Laursen wrote:
>>
>> OK, I should have upgraded. But I am currently travelling an with a small
>> laptop only and an Internet connectivity not fit for downloads (call it a
>> bad excuse if you want! :-) )
>>
>> So it actually INSERTS. That is nice. But does it return an error or
>> warning or nothing? It should not be an error IMO as various clients would
>> 'abort on error' and flood its log with error messages.
>>
>> -- Peter
>>
>> On Fri, Nov 6, 2015 at 11:32 AM, Ian Gilfillan <i...@mariadb.org> wrote:
>>
>>>
>>> 06/11/2015 07:51, Peter Laursen wrote:
>>>
>>>> I reported this bug report to Oracle:
>>>> <http://bugs.mysql.com/bug.php?id=79148>
>>>> http://bugs.mysql.com/bug.php?id=79148
>>>>
>>>> It is almost the same in MariaDB - but the error message is different,
>>>> see
>>>>
>>>> SELECT VERSION(); -- 10.1.2-MariaDB-log
>>>>
>>>> CREATE TABLE `vc_test`.`t1`(
>>>>   `id` INT NOT NULL,
>>>>   `id3` INT AS ( id*3 ) VIRTUAL
>>>> );
>>>>
>>>> INSERT INTO `vc_test`.`t1` VALUES (1,3);
>>>> -- retruns: Error Code: 1906 - The value specified for computed column
>>>> 'id3' in table 't1' ignored
>>>>
>>>> SELECT * FROM t1;
>>>> -- returns empty set
>>>>
>>>>
>>>> So here the error message is that "value is ignored" (not that it is
>>>> "not allowed").  It looks to me like somebody in MariaDB actually
>>>> identified the problem, but forgot to finish things.
>>>>
>>>> The statement should succeed (maybe raise a warning), and the
>>>> "specified value should be ignored" as the error message says, but what it
>>>> in reality is not.
>>>>
>>>> What say?
>>>>
>>>
>>> In 10.1.8, the above returns:
>>> SELECT * FROM t1;
>>> ++--+
>>> | id | id3  |
>>> ++--+
>>> |  1 |3 |
>>> ++--+
>>>
>>>
>>
>> ___
>> Mailing list: https://launchpad.net/~maria-developers
>> Post to : maria-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~maria-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Virtual columns and 'mysqldump' (and similar)

[Peter Laursen]

OK, I should have upgraded. But I am currently travelling an with a small
laptop only and an Internet connectivity not fit for downloads (call it a
bad excuse if you want! :-) )

So it actually INSERTS. That is nice. But does it return an error or
warning or nothing? It should not be an error IMO as various clients would
'abort on error' and flood its log with error messages.

-- Peter

On Fri, Nov 6, 2015 at 11:32 AM, Ian Gilfillan <i...@mariadb.org> wrote:

>
> 06/11/2015 07:51, Peter Laursen wrote:
>
>> I reported this bug report to Oracle:
>> http://bugs.mysql.com/bug.php?id=79148
>>
>> It is almost the same in MariaDB - but the error message is different, see
>>
>> SELECT VERSION(); -- 10.1.2-MariaDB-log
>>
>> CREATE TABLE `vc_test`.`t1`(
>>   `id` INT NOT NULL,
>>   `id3` INT AS ( id*3 ) VIRTUAL
>> );
>>
>> INSERT INTO `vc_test`.`t1` VALUES (1,3);
>> -- retruns: Error Code: 1906 - The value specified for computed column
>> 'id3' in table 't1' ignored
>>
>> SELECT * FROM t1;
>> -- returns empty set
>>
>>
>> So here the error message is that "value is ignored" (not that it is "not
>> allowed").  It looks to me like somebody in MariaDB actually identified the
>> problem, but forgot to finish things.
>>
>> The statement should succeed (maybe raise a warning), and the "specified
>> value should be ignored" as the error message says, but what it in reality
>> is not.
>>
>> What say?
>>
>
> In 10.1.8, the above returns:
> SELECT * FROM t1;
> ++--+
> | id | id3  |
> ++--+
> |  1 |3 |
> ++--+
>
>
> ___
> Mailing list: https://launchpad.net/~maria-developers
> Post to : maria-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~maria-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Virtual columns and 'mysqldump' (and similar)

[Peter Laursen]

yup .. this is good!

SELECT VERSION(); -- 10.1.8-MariaDB

CREATE DATABASE vctest;
USE vctest;

CREATE TABLE `t1`(
  `id` INT NOT NULL,
  `id3` INT AS ( id*3 ) VIRTUAL
);

INSERT INTO `t1` VALUES (1,3);
-- retruns: Error Code: 1906 - The value specified for computed column
'id3' in table 't1' ignored

SHOW WARNINGS;
-- 1906  The value specified for computed column 'id3' in table 't1' ignored

SELECT * FROM t1;
/*
id id3
--  
 1 3
*/

On Fri, Nov 6, 2015 at 11:52 AM, Ian Gilfillan <i...@mariadb.org> wrote:

> The insert statement returns a warning:
>
> INSERT INTO `test`.`t1` VALUES (1,3);
> Query OK, 1 row affected, 1 warning (0.07 sec)
>
> Warning (Code 1906): The value specified for computed column 'id3' in
> table 't1' ignored
>
>
>
> On 06/11/2015 08:09, Peter Laursen wrote:
>
> OK, I should have upgraded. But I am currently travelling an with a small
> laptop only and an Internet connectivity not fit for downloads (call it a
> bad excuse if you want! :-) )
>
> So it actually INSERTS. That is nice. But does it return an error or
> warning or nothing? It should not be an error IMO as various clients would
> 'abort on error' and flood its log with error messages.
>
> -- Peter
>
> On Fri, Nov 6, 2015 at 11:32 AM, Ian Gilfillan <i...@mariadb.org> wrote:
>
>>
>> 06/11/2015 07:51, Peter Laursen wrote:
>>
>>> I reported this bug report to Oracle:
>>> <http://bugs.mysql.com/bug.php?id=79148>
>>> http://bugs.mysql.com/bug.php?id=79148
>>>
>>> It is almost the same in MariaDB - but the error message is different,
>>> see
>>>
>>> SELECT VERSION(); -- 10.1.2-MariaDB-log
>>>
>>> CREATE TABLE `vc_test`.`t1`(
>>>   `id` INT NOT NULL,
>>>   `id3` INT AS ( id*3 ) VIRTUAL
>>> );
>>>
>>> INSERT INTO `vc_test`.`t1` VALUES (1,3);
>>> -- retruns: Error Code: 1906 - The value specified for computed column
>>> 'id3' in table 't1' ignored
>>>
>>> SELECT * FROM t1;
>>> -- returns empty set
>>>
>>>
>>> So here the error message is that "value is ignored" (not that it is
>>> "not allowed").  It looks to me like somebody in MariaDB actually
>>> identified the problem, but forgot to finish things.
>>>
>>> The statement should succeed (maybe raise a warning), and the "specified
>>> value should be ignored" as the error message says, but what it in reality
>>> is not.
>>>
>>> What say?
>>>
>>
>> In 10.1.8, the above returns:
>> SELECT * FROM t1;
>> ++--+
>> | id | id3  |
>> ++--+
>> |  1 |3 |
>> ++--+
>>
>>
>
> ___
> Mailing list: https://launchpad.net/~maria-developers
> Post to : maria-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~maria-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] passwordless mariadb root login with auht_socket in Debian

[Peter Laursen]

DELIMITERs are (should be) definitely handled in the client. The server
does not know about it. It is also not listed here
http://dev.mysql.com/doc/refman/5.6/en/sql-syntax.html for same reason.

-- Peter

On Tue, Feb 24, 2015 at 3:05 AM, Daniel Black daniel.bl...@openquery.com
wrote:



 - Original Message -
  Manually executing the command result in this error :
   ERROR: 1064  You have an error in your SQL syntax; check the
  manual that corresponds to your MariaDB server version for the right
  syntax to use near 'USE mysql;DELIMITER //; CREATE PROCEDURE
  debian_plugin_install(IN plugin_name C' at line 1
   150223 22:44:06 [ERROR] Aborting
 
  By adding \n between each of these statements we can see that the
  statement causing the syntax error is DELIMITER //;, it seems that
  DELIMITER is only used by mysql client and the that mysqld doesnt
  recognize it as an internal command.

 thank you


 --
 --
 Daniel Black, Engineer @ Open Query (http://openquery.com.au)
 Remote expertise  maintenance for MySQL/MariaDB server environments.

 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Interest in Contributing to MariaDB and participation in GSoC 2015

[Peter Laursen]

I don't know if the MariaDB people have this priority, but inplementing
CHECK CONSTRAINTS always was an omission in MySQL. You may specify such
currently in CREATE/ALTER TABLE. but it is silently ignored.


-- Peter
-- Webyog

On Mon, Feb 9, 2015 at 6:47 AM, Jonas Oreland jon...@google.com wrote:

 Fyi: we have already fixed 4991 (after having quickly browsed the MDEV)...
 i'll try to contribute it shortly

 /Jonas

 On Sun, Feb 8, 2015 at 3:28 PM, Kristian Nielsen kniel...@knielsen-hq.org
  wrote:

 Sergei Golubchik s...@mariadb.org writes:

  On Jan 24, Tekang Check wrote:

  the 2015 round of the Google Summer of Code. While looking at the
 projects.
  I'm interested in Database replication and would love to do some work
 in

  Take a look at
 
https://mariadb.atlassian.net/issues/?jql=labels%3Dgsoc15
 
  and don't hesitate to ask if something isn't clear.

 If you are interested in replication, I would recommend this task in
 particular:

 MDEV-4991: GTID binlog indexing
 https://mariadb.atlassian.net/browse/MDEV-4991

 This is an important task, as it solves a bottleneck that currently exists
 when many slave servers connect to one master. And it should be
 interesting to
 work on, I think.

  - Kristian.

 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp



 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] MDEV-7286 TRIGGER: CREATE OR REPLACE, CREATE IF NOT EXISTS

[Peter Laursen]

As regards TRIGGERS in MySQL I am very much missing what PostgreSQL (and
maybe other RDBMS as well) has: an option to [temporarily] disable
TRIGGGER[S] for all or specific users - like listed in PostgreSQL docs: (
http://www.postgresql.org/docs/9.2/static/sql-altertable.html)

ALTER TABLE
..
DISABLE TRIGGER [ trigger_name | ALL | USER ]
ENABLE TRIGGER [ trigger_name | ALL | USER ]
..

A TRIGGER may work fine with the application it was designed to be used
with. But you may need to do some manual maintenance and then it is not
always desirable that TRIGGERS will fire. It can actually start a chain of
unwanted changes that can be very dificult to correct (unless you resort to
the brutal solution of taking the database offline, dropping TRIGGERS, do
the maintenance and recreate the TRIGGERS).



(unrelated to the code review requested, of course).



-- Peter

On Mon, Feb 9, 2015 at 1:44 PM, Alexander Barkov b...@mariadb.org wrote:

   Hi Serg,

 Please review a patch for MDEV-7286.

 Thanks.

 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Dynamic columns support in libmaria client library?

[Peter Laursen]

Can't we then have LGPL *clones* bundled with libmariadb?


-- Peter

On Tue, Jan 27, 2015 at 11:51 PM, Oleksandr Byelkin sa...@montyprogram.com
wrote:

 Hi!

 On 27.01.15 21:09, Peter Laursen wrote:
 [skip]



 Now can ma_dyncol.h be linked against libmaria as well?

 There are 2 questions actually
 1) technical: will it work with libmaria?

  yes it should


 2) legal: can a client program using libmaria under LGPL license
 include ma_dyncol.h?

  ma_dyncol.h  ma_dyncol.c are not GPL (see files) so I'd say yes (but I
 have to admit that I am not lawyer so I am sure only 99%).

 [skip]

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Dynamic columns support in libmaria client library?

[Peter Laursen]

Is it not possible to have a reply here?


--Peter

On Fri, Dec 26, 2014 at 1:28 PM, Peter Laursen peter_laur...@webyog.com
wrote:

 This page
 https://mariadb.com/kb/en/mariadb/documentation/nosql/dynamic-columns-api/
 does not mention anything about it. it  just says

 *The API is a part of libmysql C client library. In order to use it, one
 needs to include this header file*
 *#include mysql/ma_dyncol.h*
 *and link against libmysql.*

 Now can ma_dyncol.h be linked against libmaria as well?

 There are 2 questions actually
 1) technical: will it work with libmaria?
 2) legal: can a client program using libmaria under LGPL license include
 ma_dyncol.h?


 -- Peter
 -- Webyog

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Renaming Virtual Columns to Computed Columns

[Peter Laursen]

Few points:

1) As regards terminology, IMHO it would be logical if 'computed' is used
as the upperlevel term. sublevel'  terms would be 'virtual' and
'persistent' (ie. a 'computed' column may be either 'virtual' or
'persistent').

2) It is not clear to me if this also proposes a change to DDL syntax used
since MariaDB 5.2  or if it is only a discussion for docs. etc.??

3) Oracle has published a MySQL 5.7 'labs' build with a similar feature. It
would be nice if some coordination could happen!  :-)


-- Peter
-- Webyog

On Mon, Jan 19, 2015 at 2:28 PM, Martijn Tonies (Upscene Productions) 
m.ton...@upscene.com wrote:

 Hello Ian,

 IMO, makes perfect sense.


 With regards,

 Martijn Tonies
 Upscene Productions
 http://www.upscene.com

 Download Database Workbench for Oracle, MS SQL Server, Sybase SQL
 Anywhere, MySQL, InterBase, NexusDB and Firebird!




 There was a suggestion on the docs mailing list that we rename Virtual
 Columns to Computed Columns. I think it makes sense, but before we
 implement I want to make sure everyone is happy with the change, so am
 repeating it here as not everyone follows docs.

 Currently, we use the term Virtual Columns (see
 https://mariadb.com/kb/en/mariadb/documentation/sql-
 structure-and-commands/sql-commands/data-definition/
 create/virtual-columns/).

 Oracle uses this term, while MS SQL and Firebird use the term Computed
 Columns to describe similar functionality.

 MariaDB's virtual column implementation has both persistent and virtual
 attributes. Talking of virtual virtual and persistent virtual can be
 confusing. Oracle's implementation, to my knowledge, only has virtual
 virtual, while MS SQL's Computed Columns offers both persistent
 (persisted in their case) and virtual.

 I think Computed is a slightly more descriptive term, and avoids the
 ambiguity of persistent virtual and virtual virtual. The MariaDB
 error messages already use the term computed, for example Constant
 expression in computed column function is not allowed.

 Unless anyone has a good reason to prefer the term virtual, we're going
 to rather use the term computed column in the docs. The article will
 still mention virtual column as an alternative etc, but computed will be
 the preferred term.

 ian


 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Dynamic columns support in libmaria client library?

[Peter Laursen]

Compare generated columns in MySQL 5.7.5 labs (refer
http://mysqlserverteam.com/generated-columns-in-mysql-5-7-5/).  It has
instrumentation in SHOW and I_S.  Please admit that this is a bug and an
oversight from MariaDB to forget about this!

FieldType NullKey


select version(); -- 5.7.5-labs-preview

create table comments(
  userid int AS (ExtractValue(comment,'/comment/userid')) STORED,
  comment TEXT,
  KEY(userid));


show columns from comments;
/*Default  Extra
---  ---  --  --  ---  -
userid   int(11)  YES MUL (NULL)   VIRTUAL
comment  text YES (NULL)
*/

describe comments;
/*
FieldType NullKey Default  Extra
---  ---  --  --  ---  -
userid   int(11)  YES MUL (NULL)   VIRTUAL
comment  text YES (NULL)
*/

show full fields from comments;
/*
FieldType Collation  NullKey Default  Extra
 Privileges   Comment
---  ---  -  --  --  ---  ---
 ---  -
userid   int(11)  (NULL) YES MUL (NULL)   VIRTUAL
 select,insert,update,references
comment  text latin1_swedish_ci  YES (NULL)
 select,insert,update,references
*/

select * from information_schema.`COLUMNS` where TABLE_NAME = 'comments';

/*
TABLE_CATALOG  TABLE_SCHEMA  TABLE_NAME  COLUMN_NAME  ORDINAL_POSITION
 COLUMN_DEFAULT  IS_NULLABLE  DATA_TYPE  CHARACTER_MAXIMUM_LENGTH
 CHARACTER_OCTET_LENGTH  NUMERIC_PRECISION  NUMERIC_SCALE
 DATETIME_PRECISION  CHARACTER_SET_NAME  COLLATION_NAME COLUMN_TYPE
 COLUMN_KEY  EXTRAPRIVILEGES   COLUMN_COMMENT
 GENERATION_EXPRESSION
-    --  ---  
 --  ---  -  
 --  -  -
 --  --  -  ---
 --  ---  ---  --
 -
deftest  commentsuserid  1
 (NULL)  YES  int  (NULL)
   (NULL) 10  0  (NULL)  (NULL)
 (NULL) int(11)  MUL VIRTUAL
 select,insert,update,references
 ExtractValue(comment,'/comment/userid')
deftest  commentscomment 2
 (NULL)  YES  text  65535
65535 (NULL) (NULL)  (NULL)  latin1
 latin1_swedish_ci  text
 select,insert,update,references

*/

On Fri, Dec 26, 2014 at 1:28 PM, Peter Laursen peter_laur...@webyog.com
wrote:

 This page
 https://mariadb.com/kb/en/mariadb/documentation/nosql/dynamic-columns-api/
 does not mention anything about it. it  just says

 *The API is a part of libmysql C client library. In order to use it, one
 needs to include this header file*
 *#include mysql/ma_dyncol.h*
 *and link against libmysql.*

 Now can ma_dyncol.h be linked against libmaria as well?

 There are 2 questions actually
 1) technical: will it work with libmaria?
 2) legal: can a client program using libmaria under LGPL license include
 ma_dyncol.h?


 -- Peter
 -- Webyog

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

[Maria-developers] Dynamic columns support in libmaria client library?

[Peter Laursen]

This page
https://mariadb.com/kb/en/mariadb/documentation/nosql/dynamic-columns-api/
does not mention anything about it. it  just says

*The API is a part of libmysql C client library. In order to use it, one
needs to include this header file*
*#include mysql/ma_dyncol.h*
*and link against libmysql.*

Now can ma_dyncol.h be linked against libmaria as well?

There are 2 questions actually
1) technical: will it work with libmaria?
2) legal: can a client program using libmaria under LGPL license include
ma_dyncol.h?


-- Peter
-- Webyog
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

[Maria-developers] COMPOUND STATEMENT fails on Windows.

[Peter Laursen]

I tried to comment on this Blog
https://blog.mariadb.org/mariadb-10-1-1-compound-statements/, but it won't
let me use my (corporate) gmail address for authencticaton. So I send
this mail instead:


I tried the example provided on Windows (both server and client are Win7 64
bit) using the command line client shipped with MariaDB 10.1:

Enter password: 
Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 5
Server version: 10.1.1-MariaDB mariadb.org binary distribution

Copyright (c) 2000, 2014, Oracle, SkySQL Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input
statement.

MariaDB [(none)] use test;
Database changed
MariaDB [test] IF @have_csv = 'YES' THEN
-   CREATE TABLE IF NOT EXISTS general_log (
- event_time TIMESTAMP(6) NOT NULL,
- user_host MEDIUMTEXT NOT NULL,
- thread_id BIGINT(21) UNSIGNED NOT NULL,
- server_id INTEGER UNSIGNED NOT NULL,
- command_type VARCHAR(64) NOT NULL,
- argument MEDIUMTEXT NOT NULL
-   ) engine=CSV CHARACTER SET utf8 comment=General log;
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual
that
corresponds to your MariaDB server version for the right syntax to use near
'' a
t line 9
MariaDB [test] END IF;

Obviously the SEMICOLON after comment=General log disturbs.  But this is
no better:

MariaDB [test] IF @have_csv = 'YES' THEN
-   CREATE TABLE IF NOT EXISTS general_log (
- event_time TIMESTAMP(6) NOT NULL,
- user_host MEDIUMTEXT NOT NULL,
- thread_id BIGINT(21) UNSIGNED NOT NULL,
- server_id INTEGER UNSIGNED NOT NULL,
- command_type VARCHAR(64) NOT NULL,
- argument MEDIUMTEXT NOT NULL
-   ) engine=CSV CHARACTER SET utf8 comment=General log
- END IF;
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual
that
corresponds to your MariaDB server version for the right syntax to use near
'END
 IF' at line 10
MariaDB [test]

What is the problem here? Is it someWindows-specific bug/issue? BTW it is
the same in SQLyog (compiled with MariaDB C-API)  as in commandline.


-- Peter
-- Webyog
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] COMPOUND STATEMENT fails on Windows.

[Peter Laursen]

Obviously I neeed to set another delimiter.  Thanks!

-- Peter

On Wed, Oct 22, 2014 at 12:40 PM, Sergei Golubchik s...@mariadb.org wrote:

 Hi, Peter!

 On Oct 22, Peter Laursen wrote:
  I tried to comment on this Blog
  https://blog.mariadb.org/mariadb-10-1-1-compound-statements/, but it
 won't
  let me use my (corporate) gmail address for authencticaton. So I send
  this mail instead:

 strange. I'll check it out.

  I tried the example provided on Windows (both server and client are Win7
 64
  bit) using the command line client shipped with MariaDB 10.1:
 
  Enter password: 
  Welcome to the MariaDB monitor.  Commands end with ; or \g.
  Your MariaDB connection id is 5
  Server version: 10.1.1-MariaDB mariadb.org binary distribution
 
  Copyright (c) 2000, 2014, Oracle, SkySQL Ab and others.
 
  Type 'help;' or '\h' for help. Type '\c' to clear the current input
  statement.
 
  MariaDB [(none)] use test;
  Database changed
  MariaDB [test] IF @have_csv = 'YES' THEN
  -   CREATE TABLE IF NOT EXISTS general_log (
  - event_time TIMESTAMP(6) NOT NULL,
  - user_host MEDIUMTEXT NOT NULL,
  - thread_id BIGINT(21) UNSIGNED NOT NULL,
  - server_id INTEGER UNSIGNED NOT NULL,
  - command_type VARCHAR(64) NOT NULL,
  - argument MEDIUMTEXT NOT NULL
  -   ) engine=CSV CHARACTER SET utf8 comment=General log;
  ERROR 1064 (42000): You have an error in your SQL syntax; check the
 manual
  that
  corresponds to your MariaDB server version for the right syntax to use
 near
  '' a
  t line 9
  MariaDB [test] END IF;
 
  Obviously the SEMICOLON after comment=General log disturbs.  But this
 is
  no better:
 ...
  What is the problem here? Is it someWindows-specific bug/issue? BTW it is
  the same in SQLyog (compiled with MariaDB C-API)  as in commandline.

 Right. It's exactly the same issue as with CREATE PROCEDURE and friends.
 If you need to enter something complex with semicolons inside, you need
 to change the delimiter. Here's an example from the manual:

 https://mariadb.com/kb/en/using-compound-statements-outside-of-stored-programs/

   MariaDB [test] delimiter |
   MariaDB [test] if @have_innodb then
 CREATE TABLE IF NOT EXISTS innodb_index_stats (
   database_nameVARCHAR(64) NOT NULL,
   table_name   VARCHAR(64) NOT NULL,
   index_name   VARCHAR(64) NOT NULL,
   last_update  TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ON
 UPDATE CURRENT_TIMESTAMP,
   stat_nameVARCHAR(64) NOT NULL,
   stat_value   BIGINT UNSIGNED NOT NULL,
   sample_size  BIGINT UNSIGNED,
   stat_description VARCHAR(1024) NOT NULL,
   PRIMARY KEY (database_name, table_name, index_name, stat_name)
 ) ENGINE=INNODB DEFAULT CHARSET=utf8 COLLATE=utf8_bin
 STATS_PERSISTENT=0;
   end if|

 Also note (the manual explains it too) that you could get a warning
 Unknown
 storage engine, despite the IF. The statement may be not executed, but
 it will be parsed anyway, and the parser can warn about unknown engine.

 Regards,
 Sergei

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Isn't thsi a bug?

[Peter Laursen]

OK .. it is not a big deal either! Thanks for replying. -- Peter

On Mon, Oct 13, 2014 at 2:35 PM, Sergei Golubchik s...@mariadb.org wrote:

 Hi, Peter!

 On Oct 06, Peter Laursen wrote:
  Refer: http://bugs.mysql.com/bug.php?id=74238
 
  here I prefer the 'relaxed parsing' in Maria DB.
 
  But look at this:
 
  CREATE TABLE `d` (
  `rec_id` INT(10) UNSIGNED NOT NULL AUTO_INCREMENT,
  `datetime` DATETIME(4) DEFAULT NULL,
  `timestamp` TIMESTAMP(4) NOT NULL DEFAULT CURRENT_TIMESTAMP(5) ON UPDATE
  CURRENT_TIMESTAMP(4),
  PRIMARY KEY (`rec_id`)
  ) ENGINE=INNODB;
  -- it actually creates the table
 
  SHOW CREATE TABLE d;
  /* returns
 
  CREATE TABLE `d` (
`rec_id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`datetime` datetime(4) DEFAULT NULL,
`timestamp` timestamp(4) NOT NULL DEFAULT CURRENT_TIMESTAMP(4) ON
 UPDATE
  CURRENT_TIMESTAMP(4),
PRIMARY KEY (`rec_id`)
  ) ENGINE=InnoDB DEFAULT CHARSET=latin1
  */
 
  I don't think DEFAULT CURRENT_TIMESTAMP(5) should be accepted for the
  datatype DATETIME(4).
 
  What say?

 I checked the code, and it happens to be intentional. If the default
 value is CURRENT_TIMESTAMP(5), it's the same as if you explicitly insert
 CURRENT_TIMESTAMP(5) into the TIMESTAMP(4) column. And you can do that -
 explicitly insert, I mean - that's not a bug, the value will be
 truncated, as expected. So, the result is exactly the same as inserting
 CURRENT_TIMESTAMP(4). That's why specifying a default of
 CURRENT_TIMESTAMP(5) is allowed - it produces the same result as a
 default of CURRENT_TIMESTAMP(4).

 On the other hand, if you insert a CURRENT_TIMESTAMP(3) value into
 TIMESTAMP(4) column - the result will be different, the last digit in
 the column will be always 0. For default values it's not supported (frm
 file does not currently remember the width for the default value).
 That's why you cannot specify a default of CURRENT_TIMESTAMP(3) for a
 TIMESTAMP(4) column.

 Regards,
 Sergei


___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Is it soon 'end of this year'?

[Peter Laursen]

Well .. where will I find it documented how to use it with Oracle-MySQL
configured for their LDAP authenticaton setup? The same code that worked
with oracles API does not work with the MariaDB API.

- Peter

On Mon, Oct 13, 2014 at 5:04 PM, Sergei Golubchik s...@mariadb.org wrote:

 Hi, Peter!

 On Sep 17, Peter Laursen wrote:
  Around ˝ year ago I discussed with some people here (Sergei G and/or
 Georg
  and/or Wlad) about support for Oracle-style plugins in the MariaDB C-API.
  The plugins include
 
  1 Windows authentication plugin
  2) Clear text plugin.
 
  At that time I was told that it could be considered 'by end end of this
  year'.
 
  1) Windows authentication plugin. Not very important, but Sergei told
 that
  he had been playing wiht it and it could probably be done in ~1 day.

 Yes. Unfortunately because of not very important part it gets
 postponed over and over.

  2) This is used by Oracle for setting up LDAP.authentication.  I am very
  well aware that there is criticism of Oracle's implementation.  But this
  does not change the fact hat people use it with servers from Oracle and
  expect clients to work with it. We get request(s) for it almost every
 week.
  So this is most important (for us).

 What about clear text plugin? It is in 5.5 and in 10.0 and, as far as I
 remember, always was there. Do you mean it doesn't work for you for some
 reason?

 Regards,
 Sergei

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Is it soon 'end of this year'?

[Peter Laursen]

I will ask here what we have. But it may never have been released,and it
that case we not have it anymore (if not committed to version control).

Including Georg Richter.  Just in case if he remembers something.


-- Peter

On Mon, Oct 13, 2014 at 5:10 PM, Roberto Spadim robe...@spadim.com.br
wrote:

 do you have the source of oracle plaintext auth plugin? i want read it

 2014-10-13 12:09 GMT-03:00 Peter Laursen peter_laur...@webyog.com:

 Well .. where will I find it documented how to use it with Oracle-MySQL
 configured for their LDAP authenticaton setup? The same code that worked
 with oracles API does not work with the MariaDB API.

 - Peter

 On Mon, Oct 13, 2014 at 5:04 PM, Sergei Golubchik s...@mariadb.org
 wrote:

 Hi, Peter!

 On Sep 17, Peter Laursen wrote:
  Around ˝ year ago I discussed with some people here (Sergei G and/or
 Georg
  and/or Wlad) about support for Oracle-style plugins in the MariaDB
 C-API.
  The plugins include
 
  1 Windows authentication plugin
  2) Clear text plugin.
 
  At that time I was told that it could be considered 'by end end of this
  year'.
 
  1) Windows authentication plugin. Not very important, but Sergei told
 that
  he had been playing wiht it and it could probably be done in ~1 day.

 Yes. Unfortunately because of not very important part it gets
 postponed over and over.

  2) This is used by Oracle for setting up LDAP.authentication.  I am
 very
  well aware that there is criticism of Oracle's implementation.  But
 this
  does not change the fact hat people use it with servers from Oracle and
  expect clients to work with it. We get request(s) for it almost every
 week.
  So this is most important (for us).

 What about clear text plugin? It is in 5.5 and in 10.0 and, as far as I
 remember, always was there. Do you mean it doesn't work for you for some
 reason?

 Regards,
 Sergei



 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp




 --
 Roberto Spadim
 SPAEmpresarial
 Eng. Automação e Controle

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Is it soon 'end of this year'?

[Peter Laursen]

OK .. we will check this again.

But in principle we want (always) not to have any external dependencies in
our prorams/apllications at at all. We link statically everything to the
extend possible. People should download and install SQlyog with a single
click and it will just work. PERIOD! :-) That is what Windows users expect
from an installer. How do we accomplish this with the MariaDB API? Compile
it as a .lib/.dll and bundle it with our installer and let the installer
copy it into the installation directory? Or should what you describe here
happen at compile-time (linking statically)? Also please remember that
SQLyog is a Windows program and our compiler is Visual Studio (2010
version, currently).

Maybe you can provide *Windowssand Visual Studio pecific* guidelines?.

Also (BTW) 1- 1½ years ago I asked similar questions and the only reply I
had was (very abstractly) that MariaDB's mplementation was far superior to
Oracle's. I was actually *despearately* asking for help at that time. The
reply (we are the best)  was very little helpful and we have already lost
significant business due to this.

Anyway, I  wili ask our developer team to recover as much information as
possible due to this.

-- Peter

On Mon, Oct 13, 2014 at 7:49 PM, Sergei Golubchik s...@mariadb.org wrote:

 Hi, Peter!

 On Oct 13, Peter Laursen wrote:
  Well .. where will I find it documented how to use it with Oracle-MySQL
  configured for their LDAP authenticaton setup? The same code that worked
  with oracles API does not work with the MariaDB API.

 There's only one difference that comes to my mind.

 Oracle-MySQL cleartext plugin is integral part of the client library,
 it's statically compiled into it. In MariaDB it's a separate plugin -
 which is loaded automatically on demand, but you still need to make sure
 you set the plugin-dir path correctly.

 There's nothing else I can think of, our test suite verifies that
 cleartext plugin exists and that it actually works, so I don't think
 we've broken it somehow.

 Regards,
 Sergei


___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Is it soon 'end of this year'?

[Peter Laursen]

To make it clear: it is not acceptable/not a usable solution for us if it
is a requirement that a MariaDB server is installed on user's system. The
client (in case SQLyog - but it could be any client) should work for
connection to remote servers with no server at all installed on client
machine.


-- Peter

On Mon, Oct 13, 2014 at 8:29 PM, Peter Laursen peter_laur...@webyog.com
wrote:

 OK .. we will check this again.

 But in principle we want (always) not to have any external dependencies in
 our prorams/apllications at at all. We link statically everything to the
 extend possible. People should download and install SQlyog with a single
 click and it will just work. PERIOD! :-) That is what Windows users expect
 from an installer. How do we accomplish this with the MariaDB API? Compile
 it as a .lib/.dll and bundle it with our installer and let the installer
 copy it into the installation directory? Or should what you describe here
 happen at compile-time (linking statically)? Also please remember that
 SQLyog is a Windows program and our compiler is Visual Studio (2010
 version, currently).

 Maybe you can provide *Windowssand Visual Studio pecific* guidelines?.

 Also (BTW) 1- 1½ years ago I asked similar questions and the only reply I
 had was (very abstractly) that MariaDB's mplementation was far superior to
 Oracle's. I was actually *despearately* asking for help at that time. The
 reply (we are the best)  was very little helpful and we have already lost
 significant business due to this.

 Anyway, I  wili ask our developer team to recover as much information as
 possible due to this.

 -- Peter

 On Mon, Oct 13, 2014 at 7:49 PM, Sergei Golubchik s...@mariadb.org
 wrote:

 Hi, Peter!

 On Oct 13, Peter Laursen wrote:
  Well .. where will I find it documented how to use it with Oracle-MySQL
  configured for their LDAP authenticaton setup? The same code that worked
  with oracles API does not work with the MariaDB API.

 There's only one difference that comes to my mind.

 Oracle-MySQL cleartext plugin is integral part of the client library,
 it's statically compiled into it. In MariaDB it's a separate plugin -
 which is loaded automatically on demand, but you still need to make sure
 you set the plugin-dir path correctly.

 There's nothing else I can think of, our test suite verifies that
 cleartext plugin exists and that it actually works, so I don't think
 we've broken it somehow.

 Regards,
 Sergei



___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Is it soon 'end of this year'?

[Peter Laursen]

Thanks .. you probabaly know that I am not a developer rmyself (I basically
stopped being so when ALGOL died 35 years ago!). I have shared all
information with SQLyog developer team and we will look into this again.


-- Peter

On Mon, Oct 13, 2014 at 9:17 PM, Sergei Golubchik s...@mariadb.org wrote:

 Hi, Peter!

 On Oct 13, Peter Laursen wrote:
  To make it clear: it is not acceptable/not a usable solution for us if it
  is a requirement that a MariaDB server is installed on user's system. The
  client (in case SQLyog - but it could be any client) should work for
  connection to remote servers with no server at all installed on client
  machine.

 Yes, I understand (and agree!).

 MariaDB server is not needed. You only need mysql_clear_password.dll
 that is put in the location where the client library expects it to. And
 you can set this location with

   mysql_options(..., MYSQL_PLUGIN_DIR, path);

 Another option would be to compile the plugin into SQLyog. It's doable
 too, but you need the source for the plugin (because it's not part of
 the libmysqlclient). Luckily, the whole source of the plugin is:

 =
 static int clear_password_auth_client(MYSQL_PLUGIN_VIO *vio, MYSQL *mysql)
 {
   int res= vio-write_packet(vio, (const unsigned char *) mysql-passwd,
  strlen(mysql-passwd) + 1);
   return res ? CR_ERROR : CR_OK;
 }

 mysql_declare_client_plugin(AUTHENTICATION)
   mysql_clear_password, Georgi Kodinov,
   Clear password authentication plugin,
   {0,1,0}, GPL, NULL, NULL, NULL, NULL,
   clear_password_auth_client
 mysql_end_client_plugin;
 =

 If you want it to be part of SQLyog, you put this code somewhere and call

   mysql_client_register_plugin(MYSQL*, _mysql_client_plugin_declaration_);

 Then you won't need a separate mysql_clear_password.dll

 Regards,
 Sergei

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

[Maria-developers] Isn't thsi a bug?

[Peter Laursen]

Refer: http://bugs.mysql.com/bug.php?id=74238

here I prefer the 'relaxed parsing' in Maria DB.


But look at this:

CREATE TABLE `d` (
`rec_id` INT(10) UNSIGNED NOT NULL AUTO_INCREMENT,
`datetime` DATETIME(4) DEFAULT NULL,
`timestamp` TIMESTAMP(4) NOT NULL DEFAULT CURRENT_TIMESTAMP(5) ON UPDATE
CURRENT_TIMESTAMP(4),
PRIMARY KEY (`rec_id`)
) ENGINE=INNODB;
-- it actually creates the table

SHOW CREATE TABLE d;
/* returns

CREATE TABLE `d` (
  `rec_id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `datetime` datetime(4) DEFAULT NULL,
  `timestamp` timestamp(4) NOT NULL DEFAULT CURRENT_TIMESTAMP(4) ON UPDATE
CURRENT_TIMESTAMP(4),
  PRIMARY KEY (`rec_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1
*/

I don't think DEFAULT CURRENT_TIMESTAMP(5) should be accepted for the
datatype DATETIME(4).


What say?



-- Peter
-- Webyog
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

[Maria-developers] Is it soon 'end of this year'?

[Peter Laursen]

Around ½ year ago I discussed with some people here (Sergei G and/or Georg
and/or Wlad) about support for Oracle-style plugins in the MariaDB C-API.
The plugins include

1 Windows authentication plugin
2) Clear text plugin.

At that time I was told that it could be considered 'by end end of this
year'.

1) Windows authentication plugin. Not very important, but Sergei told that
he had been playing wiht it and it could probably be done in ~1 day.

2) This is used by Oracle for setting up LDAP.authentication.  I am very
well aware that there is criticism of Oracle's implementation.  But this
does not change the fact hat people use it with servers from Oracle and
expect clients to work with it. We get request(s) for it almost every week.
So this is most important (for us).


Any chance that those can soon be prioritized?



(if you feel your self mis-quoted then I apologize)..

-- Peter
--Webyog
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Question about GTIDs in MariaBD

[Peter Laursen]

@AL13N ... it affects scripts generated by an automatic maintenance tool.
 The tool does updates to multiple tables in one transaction and does not
check for the storage engine. It used to work, but now fails on schemas
that have a mix of MyISAM and InnoDB tables. (simplifed explanation!)

-- Peter


On Sun, May 11, 2014 at 10:44 PM, AL13N al...@mageia.org wrote:

 Op zondag 11 mei 2014 16:59:10 schreef Peter Laursen:
  With autocommit=1 every statement runs in its own transaction, so
  obviousluy .. yes!
 
  MyISAM is/used to be completely  'transaction-agnosstic'.  But GTIDs seem
  to confict with non-transactional storage engines (as far as I can
  understand). MySQL/Oracle have solved (!) this by not allowing updates
 to
  tables using  transactional engines and non-transactional storage engines
  in same transaction.


 I don't get this... if MyISAM is transaction-agnostic, why would you use
 it in
 a transaction to begin with and even combined with a transactional
 database?

 it seems to me that if you rely on something like this, one shouldn't use
 MyISAM, or expect it to cope with this... (even though this example should
 be
 safe), (well, because it's transaction-agnostic, one can't asume it uses
 the
 same values when using transactional storage engines?

 of course, i'm not an expert, so i probably get a wrong idea of the
 problem.

 Is there some kind of example that _is_ unsafe somehow? wrt GTID being
 conflicting? since you speak of GTID, i assume you mean the replication
 safety?
 (ie: different results?)


  However to me it is nonsense that transactions apply (have any effect at
  all) for non-transactional storage engines.  As a consequence I consider
  this solution (what must have been enforced in the server layer and not
 the
  storeage engine layer) by Oracle 'a dirty hack' (unless somewone can
  explain me why it it necessary).
 
  -- Peter
 
  On Sun, May 11, 2014 at 4:42 PM, Roberto Spadim
 robe...@spadim.com.brwrote:
   With autoclmmit=1 works?
  
   Em domingo, 11 de maio de 2014, Peter Laursen 
 peter_laur...@webyog.com
   escreveu:
  
   Thanks for the reply, but I am afraid I don't fully understand.
  
   Here is a simple test case with mySQL 5.6.17:
  
   1)
   You need all those in configuration [mysqld) section
  
   log-bin
   log-slave-updates
   gtid_mode = ON
   enforce_gtid_consistency = ON
  
  
   2)
   Then this small script will reproduce:
  
  
   DROP DATABASE IF EXISTS `gtid_test`;
   CREATE DATABASE `gtid_test`;
   USE `gtid_test`;
  
   CREATE TABLE `tab1` (
   `a` INT DEFAULT NULL
   ) ENGINE=MYISAM ;
  
   CREATE TABLE `tab2` (
   `b` INT
   ) ENGINE=INNODB;
  
   --start a transaction
   SET autocommit=0;
  
   INSERT INTO `tab1` VALUES (1);
   INSERT INTO `tab2` VALUES (1);
  
   -- now the first UPDATE to the MyISAM table in the transaction
 triggers
   this error:
  
   UPDATE `tab1` SET `a` = 5 WHERE `a` = 1;
  
   -- and you'll get:
   --
   -- Error Code: 1785
   -- When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, updates to
   non-transactional tables can only be done in either autocommitted
   statements or single-statement transactions, and never in the same
   statement as updates to transactional tables.
  
  
   3)
   ShouldI understand that MariaDB dos not prevent this (does not raise
 an
   error), but it is still unsafe as binlog - and thus replication - may
 be
   corrupted?
  
  
   Thanks!
  
   -- Peter
  
   On Sat, May 10, 2014 at 6:09 PM, Pavel Ivanov piva...@google.com
 wrote:
   There is no such limitation in MariaDB as well as no limitation on
   CREATE TABLE ... SELECT.
  
   Although beware that mixing statements changing MyISAM and InnoDB
   tables in statement binlog mode you may get different results from
 the
   statements on slaves.
  
   Pavel
  
   On Sat, May 10, 2014 at 3:48 AM, Peter Laursen
   peter_laur...@webyog.com
  
   wrote:
GTID implementation in MySQL 5.6 has the limitation as described
 here:
  
 https://dev.mysql.com/doc/refman/5.6/en/replication-gtids-restrictions.h
   tml
  
nontransactional storage engines such as MyISAM cannot be made in
 the
  
   same
  
statement or transaction as updates to tables using transactional
  
   storage
  
engines such as InnoDB.
   
If you try you will get the error:
Error Code: 1785
When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, updates to
  
   non-transactional
  
tables can only be done in either autocommitted statements or
single-statement transactions, and never in the same statement as
  
   updates to
  
transactional tables.
   
Is there same or similar/other limitations with GTID in MariaDB 10?
   
-- Peter Laursen
-- Webyog
   
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Question about GTIDs in MariaBD

[Peter Laursen]

I blogged this:
http://blog.webyog.com/2014/05/12/suddenly-myisam-became-transaction-aware/

It should appear on planet.mysql.com soon.

-- Peter


On Mon, May 12, 2014 at 10:53 AM, Kristian Nielsen kniel...@knielsen-hq.org
 wrote:

 AL13N al...@rmail.be writes:

  Peter Laursen peter_laur...@webyog.com writes:

  So yes, there are others that consider Oracle's design of GTID 'a dirty
  hack',
  but MariaDB 10.0 GTID is not affected by that design.

  What about mariadb being a slave of a Oracle MySQL GTID?

 The restrictions are on the master, not on the slaves. So what do you mean?
 Surely, connecting a MariaDB slave to an Oracle MySQL master will not
 remove
 those restrictions.

 Note that when a MariaDB server connects as a slave to an Oracle MySQL
 master
 server, it is not possible to use GTID for that connection (because the
 GTID
 implementations are not compatible). Old style non-GTID replication must be
 used.

  - Kristian.

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Question about GTIDs in MariaBD

[Peter Laursen]

Thanks for the reply, but I am afraid I don't fully understand.

Here is a simple test case with mySQL 5.6.17:

1)
You need all those in configuration [mysqld) section

log-bin
log-slave-updates
gtid_mode = ON
enforce_gtid_consistency = ON


2)
Then this small script will reproduce:


DROP DATABASE IF EXISTS `gtid_test`;
CREATE DATABASE `gtid_test`;
USE `gtid_test`;

CREATE TABLE `tab1` (
`a` INT DEFAULT NULL
) ENGINE=MYISAM ;

CREATE TABLE `tab2` (
`b` INT
) ENGINE=INNODB;

--start a transaction
SET autocommit=0;

INSERT INTO `tab1` VALUES (1);
INSERT INTO `tab2` VALUES (1);

-- now the first UPDATE to the MyISAM table in the transaction triggers
this error:

UPDATE `tab1` SET `a` = 5 WHERE `a` = 1;

-- and you'll get:
-- 
-- Error Code: 1785
-- When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, updates to non-transactional
tables can only be done in either autocommitted statements or
single-statement transactions, and never in the same statement as updates
to transactional tables.


3)
ShouldI understand that MariaDB dos not prevent this (does not raise an
error), but it is still unsafe as binlog - and thus replication - may be
corrupted?


Thanks!

-- Peter

On Sat, May 10, 2014 at 6:09 PM, Pavel Ivanov piva...@google.com wrote:

 There is no such limitation in MariaDB as well as no limitation on
 CREATE TABLE ... SELECT.

 Although beware that mixing statements changing MyISAM and InnoDB
 tables in statement binlog mode you may get different results from the
 statements on slaves.

 Pavel

 On Sat, May 10, 2014 at 3:48 AM, Peter Laursen peter_laur...@webyog.com
 wrote:
  GTID implementation in MySQL 5.6 has the limitation as described here:
 
 https://dev.mysql.com/doc/refman/5.6/en/replication-gtids-restrictions.html
 
 
  nontransactional storage engines such as MyISAM cannot be made in the
 same
  statement or transaction as updates to tables using transactional storage
  engines such as InnoDB.
 
  If you try you will get the error:
  Error Code: 1785
  When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, updates to non-transactional
  tables can only be done in either autocommitted statements or
  single-statement transactions, and never in the same statement as
 updates to
  transactional tables.
 
  Is there same or similar/other limitations with GTID in MariaDB 10?
 
  -- Peter Laursen
  -- Webyog
 
  ___
  Mailing list: https://launchpad.net/~maria-developers
  Post to : maria-developers@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~maria-developers
  More help   : https://help.launchpad.net/ListHelp
 

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Question about GTIDs in MariaBD

[Peter Laursen]

With autocommit=1 every statement runs in its own transaction, so
obviousluy .. yes!

MyISAM is/used to be completely  'transaction-agnosstic'.  But GTIDs seem
to confict with non-transactional storage engines (as far as I can
understand). MySQL/Oracle have solved (!) this by not allowing updates to
tables using  transactional engines and non-transactional storage engines
in same transaction.

However to me it is nonsense that transactions apply (have any effect at
all) for non-transactional storage engines.  As a consequence I consider
this solution (what must have been enforced in the server layer and not the
storeage engine layer) by Oracle 'a dirty hack' (unless somewone can
explain me why it it necessary).

-- Peter


On Sun, May 11, 2014 at 4:42 PM, Roberto Spadim robe...@spadim.com.brwrote:

 With autoclmmit=1 works?

 Em domingo, 11 de maio de 2014, Peter Laursen peter_laur...@webyog.com
 escreveu:

 Thanks for the reply, but I am afraid I don't fully understand.

 Here is a simple test case with mySQL 5.6.17:

 1)
 You need all those in configuration [mysqld) section

 log-bin
 log-slave-updates
 gtid_mode = ON
 enforce_gtid_consistency = ON


 2)
 Then this small script will reproduce:


 DROP DATABASE IF EXISTS `gtid_test`;
 CREATE DATABASE `gtid_test`;
 USE `gtid_test`;

 CREATE TABLE `tab1` (
 `a` INT DEFAULT NULL
 ) ENGINE=MYISAM ;

 CREATE TABLE `tab2` (
 `b` INT
 ) ENGINE=INNODB;

 --start a transaction
 SET autocommit=0;

 INSERT INTO `tab1` VALUES (1);
 INSERT INTO `tab2` VALUES (1);

 -- now the first UPDATE to the MyISAM table in the transaction triggers
 this error:

 UPDATE `tab1` SET `a` = 5 WHERE `a` = 1;

 -- and you'll get:
 --
 -- Error Code: 1785
 -- When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, updates to
 non-transactional tables can only be done in either autocommitted
 statements or single-statement transactions, and never in the same
 statement as updates to transactional tables.


 3)
 ShouldI understand that MariaDB dos not prevent this (does not raise an
 error), but it is still unsafe as binlog - and thus replication - may be
 corrupted?


 Thanks!

 -- Peter

 On Sat, May 10, 2014 at 6:09 PM, Pavel Ivanov piva...@google.com wrote:

 There is no such limitation in MariaDB as well as no limitation on
 CREATE TABLE ... SELECT.

 Although beware that mixing statements changing MyISAM and InnoDB
 tables in statement binlog mode you may get different results from the
 statements on slaves.

 Pavel

 On Sat, May 10, 2014 at 3:48 AM, Peter Laursen peter_laur...@webyog.com
 wrote:
  GTID implementation in MySQL 5.6 has the limitation as described here:
 
 https://dev.mysql.com/doc/refman/5.6/en/replication-gtids-restrictions.html
 
 
  nontransactional storage engines such as MyISAM cannot be made in the
 same
  statement or transaction as updates to tables using transactional
 storage
  engines such as InnoDB.
 
  If you try you will get the error:
  Error Code: 1785
  When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, updates to
 non-transactional
  tables can only be done in either autocommitted statements or
  single-statement transactions, and never in the same statement as
 updates to
  transactional tables.
 
  Is there same or similar/other limitations with GTID in MariaDB 10?
 
  -- Peter Laursen
  -- Webyog
 
  ___
  Mailing list: https://launchpad.net/~maria-developers
  Post to : maria-developers@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~maria-developers
  More help   : https://help.launchpad.net/ListHelp
 




 --
 Roberto Spadim
 SPAEmpresarial
 Eng. Automação e Controle


___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

[Maria-developers] Question about GTIDs in MariaBD

[Peter Laursen]

GTID implementation in MySQL 5.6 has the limitation as described here:
https://dev.mysql.com/doc/refman/5.6/en/replication-gtids-restrictions.html


nontransactional storage engines such as
MyISAMhttps://dev.mysql.com/doc/refman/5.6/en/myisam-storage-engine.html
cannot
be made in the same statement or transaction as updates to tables using
transactional storage engines such as
InnoDBhttps://dev.mysql.com/doc/refman/5.6/en/innodb-storage-engine.html
.

If you try you will get the error:
Error Code: 1785
When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, updates to non-transactional tables
can only be done in either autocommitted statements or single-statement
transactions, and never in the same statement as updates to transactional
tables.

Is there same or similar/other limitations with GTID in MariaDB 10?

-- Peter Laursen
-- Webyog
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

[Maria-developers] MariaDB C-API and specific P_S tables

[Peter Laursen]

THis is probably a question that Gerog Richter (or possibly Wlad) could
reply to.

I came across this bug report:
http://bugs.mysql.com/bug.php?id=71801
.. files by former MySQL/Sun/Oracle supporter Veleriuy Kravtchuk

We have a 64 bit C-application compiled with MariaDB C-API (on and for
Windows 64 bit). I connect to MySQL 5.6.15 and execute

SELECT * FROM `session_connect_attrs`;

/*
PROCESSLIST_ID ATTR_NAME ATTR_VALUE ORDINAL_POSITION
-- --- -- --
2 _os Windows 0
2 _client_name libmariadb 1
2 _pid 5012 2
2 _thread 4640 3
2 _platform x86 4
2 _client_version 1.1.2 5
*/

With the MySQL CLI 5.6.15, you will get

/*
PROCESSLIST_ID ATTR_NAME ATTR_VALUE ORDINAL_POSITION
-- --- -- --
4 _os Win64 0
4 _client_name libmysql 1
4 _pid 4888 2
4 _thread 4320 3
4 _platform x86_64 4
4 program_name mysql 5
4 _client_version 5.6.15 6
*/

The differences I notice are

* Our application populates P_S with Windows - not Win64 as the 5.6.15
CLI
* Our application populates 'P_S with x86 and not x86_64.
* Our application does not populate P_S with a program_name. But it has a
name of course!

MySQL 5.6 docs at
http://dev.mysql.com/doc/refman/5.6/en/performance-schema-connection-attribute-tables.htmllists
(as far as I can understand)  that the client should use
mysql_options() and mysql_options4() C API functions to populate P_S with
all information.


I have two questions:

1)
Will the first 2 differences listed require a patch in our code or in
libmariadb?

2)
Obviosuly the lacking program name in the P_S tables is something that we
will neeed to take care of ourselves. However I think that mysql_options4()
was added in MySQL 5.6 and the MariaDB API does not supprot it currently
(it is targeted to be compatible with Oracle 5.5 API, I think). And to
populate the program name we may need to use  mysql_options4(). Am I right?
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] MariaDB C-API and specific P_S tables

[Peter Laursen]

BTW: the two tables do not exist in P_S in MariaDB 10.0.8

-- Peter


On Mon, Feb 24, 2014 at 4:02 PM, Peter Laursen peter_laur...@webyog.comwrote:


 THis is probably a question that Gerog Richter (or possibly Wlad) could
 reply to.

 I came across this bug report:
 http://bugs.mysql.com/bug.php?id=71801
 .. files by former MySQL/Sun/Oracle supporter Veleriuy Kravtchuk

 We have a 64 bit C-application compiled with MariaDB C-API (on and for
 Windows 64 bit). I connect to MySQL 5.6.15 and execute

 SELECT * FROM `session_connect_attrs`;

 /*
 PROCESSLIST_ID ATTR_NAME ATTR_VALUE ORDINAL_POSITION
 -- --- -- --
 2 _os Windows 0
 2 _client_name libmariadb 1
 2 _pid 5012 2
 2 _thread 4640 3
 2 _platform x86 4
 2 _client_version 1.1.2 5
 */

 With the MySQL CLI 5.6.15, you will get

 /*
 PROCESSLIST_ID ATTR_NAME ATTR_VALUE ORDINAL_POSITION
 -- --- -- --
 4 _os Win64 0
 4 _client_name libmysql 1
 4 _pid 4888 2
 4 _thread 4320 3
 4 _platform x86_64 4
 4 program_name mysql 5
 4 _client_version 5.6.15 6
 */

 The differences I notice are

 * Our application populates P_S with Windows - not Win64 as the 5.6.15
 CLI
 * Our application populates 'P_S with x86 and not x86_64.
 * Our application does not populate P_S with a program_name. But it has
 a name of course!

 MySQL 5.6 docs at
 http://dev.mysql.com/doc/refman/5.6/en/performance-schema-connection-attribute-tables.htmllists
  (as far as I can understand)  that the client should use
 mysql_options() and mysql_options4() C API functions to populate P_S with
 all information.


 I have two questions:

 1)
 Will the first 2 differences listed require a patch in our code or in
 libmariadb?

 2)
 Obviosuly the lacking program name in the P_S tables is something that we
 will neeed to take care of ourselves. However I think that mysql_options4()
 was added in MySQL 5.6 and the MariaDB API does not supprot it currently
 (it is targeted to be compatible with Oracle 5.5 API, I think). And to
 populate the program name we may need to use  mysql_options4(). Am I right?



___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] MariaDB C-API and specific P_S tables

[Peter Laursen]

SELECT VERSION(); -- returns 10.0.8-MariaDB
USE `performance_schema`;
SHOW TABLES LIKE 'session%'; -- empty set

.. but  maybe I should run rememer to run mysql_upgrade before complaining
about such things! :-)


I will update in a couple of hours if mysql_upgrade did the trick. If not
it could be Win-only problem.


-- Peter


On Mon, Feb 24, 2014 at 5:47 PM, Sergei Golubchik s...@mariadb.org wrote:

 Hi, Peter!

 On Feb 24, Peter Laursen wrote:
  BTW: the two tables do not exist in P_S in MariaDB 10.0.8

 What tables don't exist?

   MariaDB [test] SELECT * FROM performance_schema.session_connect_attrs;
   ++-++--+
   | PROCESSLIST_ID | ATTR_NAME   | ATTR_VALUE | ORDINAL_POSITION |
   ++-++--+
   |  2 | _os | Linux  |0 |
   |  2 | _client_name| libmysql   |1 |
   |  2 | _pid| 28713  |2 |
   |  2 | _client_version | 10.0.8 |3 |
   |  2 | _platform   | x86_64 |4 |
   |  2 | program_name| mysql  |5 |
   ++-++--+
   6 rows in set (0.00 sec)

   MariaDB [test] SELECT VERSION();
   +--+
   | VERSION()|
   +--+
   | 10.0.8-MariaDB-debug |
   +--+
   1 row in set (0.00 sec)

 Regards,
 Sergei

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] MariaDB C-API and specific P_S tables

[Peter Laursen]

Running mysql_upgrade did the trick.  Sorry!


C:\Program Files\MariaDB 10.0\binmysql_upgrade -uroot -p --port=3313
Enter password: 
Phase 1/3: Fixing table and database names
Phase 2/3: Checking and upgrading tables
Processing databases
information_schema
mysql
mysql.columns_priv OK
mysql.db OK
..
..
Phase 3/3: Running 'mysql_fix_privilege_tables'...
OK

C:\Program Files\MariaDB 10.0\binmysql -uroot -p --port=3313
Enter password: 
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 13
Server version: 10.0.8-MariaDB mariadb.org binary distribution

Copyright (c) 2000, 2013, Oracle, Monty Program Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input
statement.

MariaDB [(none)] use performance_schema;
Database changed
MariaDB [performance_schema] show tables like 'session%';
+-+
| Tables_in_performance_schema (session%) |
+-+
| session_account_connect_attrs |
| session_connect_attrs |
+-+
2 rows in set (0.00 sec)

MariaDB [performance_schema] exit
Bye

C:\Program Files\MariaDB 10.0\bin


-- Peter


On Mon, Feb 24, 2014 at 7:29 PM, Peter Laursen peter_laur...@webyog.comwrote:

 SELECT VERSION(); -- returns 10.0.8-MariaDB
 USE `performance_schema`;
 SHOW TABLES LIKE 'session%'; -- empty set

 .. but  maybe I should run rememer to run mysql_upgrade before complaining
 about such things! :-)


 I will update in a couple of hours if mysql_upgrade did the trick. If not
 it could be Win-only problem.


 -- Peter


 On Mon, Feb 24, 2014 at 5:47 PM, Sergei Golubchik s...@mariadb.orgwrote:

 Hi, Peter!

 On Feb 24, Peter Laursen wrote:
  BTW: the two tables do not exist in P_S in MariaDB 10.0.8

 What tables don't exist?

   MariaDB [test] SELECT * FROM performance_schema.session_connect_attrs;
   ++-++--+
   | PROCESSLIST_ID | ATTR_NAME   | ATTR_VALUE | ORDINAL_POSITION |
   ++-++--+
   |  2 | _os | Linux  |0 |
   |  2 | _client_name| libmysql   |1 |
   |  2 | _pid| 28713  |2 |
   |  2 | _client_version | 10.0.8 |3 |
   |  2 | _platform   | x86_64 |4 |
   |  2 | program_name| mysql  |5 |
   ++-++--+
   6 rows in set (0.00 sec)

   MariaDB [test] SELECT VERSION();
   +--+
   | VERSION()|
   +--+
   | 10.0.8-MariaDB-debug |
   +--+
   1 row in set (0.00 sec)

 Regards,
 Sergei



___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] parallel replication monitoring

[Peter Laursen]

useful to have in I_S or P_S.  I vote for I_S. P_S may be disabled by
admin due to its memory and cpu overhead.

-- Peter
-- Webyog


On Fri, Nov 15, 2013 at 11:20 AM, Kristian Nielsen kniel...@knielsen-hq.org
 wrote:

 Giuseppe Maxia g.ma...@gmail.com writes:

  * which database they are running is important even if the parallel
  replication is not split by schema. As a DBA, I need to know at a glance
  where the action is occurring. SHOW PROCESSLIST gives me that
 information,
  but it doesn't tell me the GTID, which is the info that gives me the
 pulse
  of the replication progress. What bothers me is that I can get either the
  GTID list or where the action is happening. Having both in one place
 should
  not be difficult (a I_S or P_S view, for example).

 Right, I think I see.

 So it could be useful to have in I_S or P_S a table that gives for each
 worker
 stuff like:

  - The GTID of the event group currently executing, or NULL if idle
  - Status (executing, waiting for prior transaction before starting,
 waiting
for prior transaction before committing, stuff like that)
  - The current database (USE xxx)
  - Currently executing query
  - Whether this worker was scheduled in parallel with something else, and
 if
so, why that was possible (group commit id or replication domain id)
  - Total number of events and event groups executed by worker thread
  - Possibly time spent idle, time spent executing, and time spent waiting
 for
prior transactions to commit (if such times can be obtained without too
high performance overhead).

 That is a nice input, thanks. Something like this would definitely be nice
 to
 have. I've put this into Jira:

 https://mariadb.atlassian.net/browse/MDEV-5296

 On top of this, I think we could also add some statistics for the SQL
 thread. Like, how often did it have to wait for a worker to become free to
 schedule a potentially parallel transaction (might indicate a too-low
 --slave-parallel-threads). And how many transactions could / could not be
 scheduled in parallel (could indicate the need to tune the master to
 provide
 more parallelism in the binlog).

 What would be really nice is to have two numbers in SHOW SLAVE STATUS. One
 is
 the wall-clock time since START SLAVE. The other is the total time spent by
 workers on executing events for this master connection (excluding waiting
 for
 other replication threads). The ratio between these two numbers would
 immediately give an indication of how effective parallel replication is at
 utilising the machine, same as the cpu% numbers in the `top` Linux utility.

  I see in mysql.gtid_slave_pos that the number of rows grows and shrinks
  while the workers are replicating, but this does not give me any useful
  information on the effectiveness of the operations

 Agree, that is mostly useless information. All except the rows with maximal
 sub_id are justa garbage rows, the deletion of which has been delayed to
 avoid
 lock contention between transactions.

  I hope to see better integration and more tools in the future. As it is
 now,
  parallel replication seems to be a very powerful engine with brake and
  steering wheel but with a blackened out dashboard. Makes for some
  adventurous driving!

 Hehe, a very nice and succinct description ;-)

 Thanks,

  - Kristian.

 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

[Maria-developers] MySQL bug affects mariaDB

[Peter Laursen]

I think the 'mysql' client with MariaDB has a similar problem as it has
with MySQL - refer?
http://bugs.mysql.com/bug.php?id=70443

MariaDB installer installs my.ini to /datadir - what with MariaDB is a
subfolder to /basedir.

The server will look for it correctly as the registry key defining the
service has a --default-file specification.  But the command line clients
don't read the registry key.


@Wlad?


-- Peter
-- Webyog
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] MySQL bug affects mariaDB

[Peter Laursen]

Thanks wlad for explanation, but this applies to 'shortcuts' (in start
menu) only I think, as I understand your reply.

If I navigate ('cd ..') to the /datadir where my.ini resides and launch
'mysql' from commnd line I will need to specify --defaults-file on the
command line, right? If not the client will start with defaults (or it will
use whatever other my.ini it finds in C:\, C:\Windows or /basedir).

?


-- Peter


On Fri, Sep 27, 2013 at 7:06 PM, Vladislav Vaintroub
w...@montyprogram.comwrote:

 The command line clients are not services, and they are not started with
 --defaults-file, this is correct.

 ** **

 But

 ** **

 1.We install shortcut to mysql client and shortcut does have
  --defaults-file , and the default-file points to the right place, i.e
 whenever you installed the mysql server instance

 On my machine (I used the default x64 installation), MySQL client shortcut
 is  this

 ** **

 C:\Windows\System32\cmd.exe /k  C:\Program Files\MariaDB
 5.5\bin\mysql.exe --defaults-file=C:\Program Files\MariaDB
 5.5\data\my.ini -uroot -p”

 ** **

 2. Out installation also provides another shortcut – called Command
 Prompt( MariaDB …)

 It could be used to call arbitrary client utilities, mysqladmin or
 somesuch .It uses yet another,  less known, trick to force client utilities
 to look for correct my.ini - it sets environment variable MYSQL_HOME to
 point to the the datadir  ( Besides, it also sets PATH to include “bin”
 directory, so that calling mysqladmin or mysql would not result in “path
 not found”)

 ** **

 The inspiration for this shortcut was a very similar feature of Visual
 Studio , the “Visual Studio 20xx Command Line”.

 ** **

 The summary of my.ini client-side support is that :

 If you install with MSI,  installer will create  shortcuts that help
 client utilities to find correct my.ini . You can have multiple versions of
 the MariaDB installed, and the shortcuts will still work correctly – every
 version specific shortcut would point to version-specific my.ini

 ** **

 Thus, I’d argue that this bug does not affect MariaDB.

 

 ** **

 ** **

 ** **

 *From:* Maria-developers [mailto:maria-developers-bounces+wlad=
 montyprogram@lists.launchpad.net] *On Behalf Of *Peter Laursen
 *Sent:* Freitag, 27. September 2013 10:06
 *To:* Maria Developers; Maria Discuss
 *Subject:* [Maria-developers] MySQL bug affects mariaDB

 ** **

 ** **

 I think the 'mysql' client with MariaDB has a similar problem as it has
 with MySQL - refer?

 http://bugs.mysql.com/bug.php?id=70443

 ** **

 MariaDB installer installs my.ini to /datadir - what with MariaDB is a
 subfolder to /basedir. 

 ** **

 The server will look for it correctly as the registry key defining the
 service has a --default-file specification.  But the command line clients
 don't read the registry key.

 ** **

 ** **

 @Wlad?

 ** **

 ** **

 -- Peter

 -- Webyog

 ** **

 ** **

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] [Maria-discuss] MySQL bug affects mariaDB

[Peter Laursen]

On Windows multiple MySQL servers run (if only they have distinct basedir,
datadir, port (and/or pipe) and service name). This is how Windows manages
servides (daemons) simply!

And BTW: this is the reason why Windows is a comfortable platform for
application testing if you want to test an application that should work
with multiple MySQL server versions. Multiple MySQL servers on *nix is a
PITA - on Windows it is an ease as the OS has no restriction in this
respect.

-- Peter


On Fri, Sep 27, 2013 at 8:12 PM, Vladislav Vaintroub
w...@montyprogram.comwrote:

 Justin, I appreciate your opinion, and if MySQL on Windows would not
 support multiple versions running on the same machine, I would agree. 

 But since we (and/or generations of programmers before me) chose to
 support multiple version of MySQL coexisting on the same machine, and I did
 not want to break it, I see no real alternative.   

 ** **

 ** **

 *From:* Justin Swanhart [mailto:greenl...@gmail.com]
 *Sent:* Freitag, 27. September 2013 19:54
 *To:* Vladislav Vaintroub
 *Cc:* Peter Laursen; Maria Developers; Maria Discuss
 *Subject:* Re: [Maria-discuss] [Maria-developers] MySQL bug affects
 mariaDB

 ** **

 Please ignore wrong block quote here - stupid mail on iPhone won't paste
 without it

 You know, windows does have easy ways to change the path and add variables
 to the environment without forcing shell invocation.  It is just that in
 the case of VS you might cross-compile or choose to compile with Vs2008 or
 vs2012 as they can be installed simultaneously.  I think if you are
 creating a service (in windows parlance) the client should know how to
 connect to the service sans hoops. Just my opinion...  VS is not the way
 most windows programs do things and you should not violate the principal if
 least surprise.



 

 --Justin


 On Sep 27, 2013, at 1:06 PM, Vladislav Vaintroub w...@montyprogram.com
 wrote:

 The command line clients are not services, and they are not started with
 --defaults-file, this is correct.

  

 But

  

 1.We install shortcut to mysql client and shortcut does have
  --defaults-file , and the default-file points to the right place, i.e
 whenever you installed the mysql server instance

 On my machine (I used the default x64 installation), MySQL client shortcut
 is  this

  

 C:\Windows\System32\cmd.exe /k  C:\Program Files\MariaDB
 5.5\bin\mysql.exe --defaults-file=C:\Program Files\MariaDB
 5.5\data\my.ini -uroot -p”

  

 2. Out installation also provides another shortcut – called Command
 Prompt( MariaDB …)

 It could be used to call arbitrary client utilities, mysqladmin or
 somesuch .It uses yet another,  less known, trick to force client utilities
 to look for correct my.ini - it sets environment variable MYSQL_HOME to
 point to the the datadir  ( Besides, it also sets PATH to include “bin”
 directory, so that calling mysqladmin or mysql would not result in “path
 not found”)

  

 The inspiration for this shortcut was a very similar feature of Visual
 Studio , the “Visual Studio 20xx Command Line”.

  

 The summary of my.ini client-side support is that :

 If you install with MSI,  installer will create  shortcuts that help
 client utilities to find correct my.ini . You can have multiple versions of
 the MariaDB installed, and the shortcuts will still work correctly – every
 version specific shortcut would point to version-specific my.ini

  

 Thus, I’d argue that this bug does not affect MariaDB.

  

  

  

 *From:* Maria-developers [
 mailto:maria-developers-bounces+wlad=montyprogram@lists.launchpad.netmaria-developers-bounces+wlad=montyprogram@lists.launchpad.net
 ] *On Behalf Of *Peter Laursen
 *Sent:* Freitag, 27. September 2013 10:06
 *To:* Maria Developers; Maria Discuss
 *Subject:* [Maria-developers] MySQL bug affects mariaDB

  

  

 I think the 'mysql' client with MariaDB has a similar problem as it has
 with MySQL - refer?

 http://bugs.mysql.com/bug.php?id=70443

  

 MariaDB installer installs my.ini to /datadir - what with MariaDB is a
 subfolder to /basedir. 

  

 The server will look for it correctly as the registry key defining the
 service has a --default-file specification.  But the command line clients
 don't read the registry key.

  

  

 @Wlad?

  

  

 -- Peter

 -- Webyog

  

  

 ___
 Mailing list: https://launchpad.net/~maria-discuss
 Post to : maria-disc...@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-discuss
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net

Re: [Maria-developers] MySQL bug affects mariaDB

[Peter Laursen]

I rarely find myself in need to use my.ini for clients.  Not me either
except for max_allowed_packet (what is implemented in both server and
client) that user want to set to INSERT table rows with photographs (.jpg's
typically) to a table.

And the 'mysql' command line client has a default max_allowed_packet of 1MB
(in the server it was raised to 4MB in MySQL 5.6 - and if I remember right
it is 8MB in recent MariaDB - but I belive the client setting is still 1MB
even in MySQL 5.6 - I have not checked though).

In contrast the C-API (both Oracle's and MariaDB's) has a defaut of 1GB
(not sure about other connectors - such as JAVA and .NET). But I am not
aware of any GUI client compiling/linking the connector with client
max_allowed_packet lowered from 1GB (the highest possible value the
protocol allows for currently).


-- Peter


On Fri, Sep 27, 2013 at 8:19 PM, Vladislav Vaintroub
w...@montyprogram.comwrote:

 Current directory does not play any role in choosing defaults file. You
 indeed need either to specify –defauilts-file, or set MYSQL_HOME, or the
 bdefault logic of finding my.ini will apply 

 On the other hand, I rarely find myself in need to use my.ini for clients.
 In doubt, I provide –port , and that’s all I need for the command line
 clients

 ** **

 *From:* Peter Laursen [mailto:peter_laur...@webyog.com]
 *Sent:* Freitag, 27. September 2013 19:15
 *To:* Vladislav Vaintroub
 *Cc:* Maria Developers; Maria Discuss
 *Subject:* Re: [Maria-developers] MySQL bug affects mariaDB

 ** **

 Thanks wlad for explanation, but this applies to 'shortcuts' (in start
 menu) only I think, as I understand your reply.  

 ** **

 If I navigate ('cd ..') to the /datadir where my.ini resides and launch
 'mysql' from commnd line I will need to specify --defaults-file on the
 command line, right? If not the client will start with defaults (or it will
 use whatever other my.ini it finds in C:\, C:\Windows or /basedir).

 ** **

 ?

 ** **

 ** **

 -- Peter

 ** **

 On Fri, Sep 27, 2013 at 7:06 PM, Vladislav Vaintroub 
 w...@montyprogram.com wrote:

 The command line clients are not services, and they are not started with
 --defaults-file, this is correct.

  

 But

  

 1.We install shortcut to mysql client and shortcut does have
  --defaults-file , and the default-file points to the right place, i.e
 whenever you installed the mysql server instance

 On my machine (I used the default x64 installation), MySQL client shortcut
 is  this

  

 C:\Windows\System32\cmd.exe /k  C:\Program Files\MariaDB
 5.5\bin\mysql.exe --defaults-file=C:\Program Files\MariaDB
 5.5\data\my.ini -uroot -p”

  

 2. Out installation also provides another shortcut – called Command
 Prompt( MariaDB …)

 It could be used to call arbitrary client utilities, mysqladmin or
 somesuch .It uses yet another,  less known, trick to force client utilities
 to look for correct my.ini - it sets environment variable MYSQL_HOME to
 point to the the datadir  ( Besides, it also sets PATH to include “bin”
 directory, so that calling mysqladmin or mysql would not result in “path
 not found”)

  

 The inspiration for this shortcut was a very similar feature of Visual
 Studio , the “Visual Studio 20xx Command Line”.

  

 The summary of my.ini client-side support is that :

 If you install with MSI,  installer will create  shortcuts that help
 client utilities to find correct my.ini . You can have multiple versions of
 the MariaDB installed, and the shortcuts will still work correctly – every
 version specific shortcut would point to version-specific my.ini

  

 Thus, I’d argue that this bug does not affect MariaDB.

  

  

  

 *From:* Maria-developers [mailto:maria-developers-bounces+wlad=
 montyprogram@lists.launchpad.net] *On Behalf Of *Peter Laursen
 *Sent:* Freitag, 27. September 2013 10:06
 *To:* Maria Developers; Maria Discuss
 *Subject:* [Maria-developers] MySQL bug affects mariaDB

  

  

 I think the 'mysql' client with MariaDB has a similar problem as it has
 with MySQL - refer?

 http://bugs.mysql.com/bug.php?id=70443

  

 MariaDB installer installs my.ini to /datadir - what with MariaDB is a
 subfolder to /basedir. 

  

 The server will look for it correctly as the registry key defining the
 service has a --default-file specification.  But the command line clients
 don't read the registry key.

  

  

 @Wlad?

  

  

 -- Peter

 -- Webyog

  

  

 ** **

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Some clarifications requested for C client

[Peter Laursen]

Could I ask for a reply here - in particular to the 2nd point about SQLite?
What is the advantage of having the SQLite codebase as part of the MariaDB
C-API as compared to getting the SQLite library from the official SQLite
webiste and link in an application?

If there is more to it than just *including the SQLite codebase*
(functionalities of any kind added due to this), then some
explanation/documentation would be nice.

-- Peter Laursen (Webyog)


On Sun, Aug 25, 2013 at 3:25 PM, Peter Laursen peter_laur...@webyog.comwrote:

 This is probably for Georg Richter (and/or @Wlad). I have a few qeustion!


 1)

 https://bazaar.launchpad.net/~maria-captains/mariadb-native-client/trunk/revision/80
 Fix for CONC-44: LOAD DATA INFILE can't open utf16le encoded filenames
 But we we can stil not specify UTF16LE as the CHARSET, I think?

 Say I have a file *named* ÄÜÑБГД.csv.  (both Western special characters
 and cyrillic characters in the file name). This file I  will be able to
 read now (using revision 80), right?

 But if file *content* is this single line (one row, two columns)

 ÄÜÑ,БГД

 and if it is encoded as 'Windows Unicode'/utf16le I still will need to
 recode the file to utf8 before executing it with LOAD DATA (as UTF16LE
 still cannot be specified for CHARSET in LOAD DATA), right?

 Please confirm that I understand this!


 2)

 https://bazaar.launchpad.net/~maria-captains/mariadb-native-client/trunk/revision/32
 Added support for embedded (sqlite).
 This happened by beginning of this year but I just noticed now.

 Now what can we actually do with SQLite and the MariaDB C-API and what we
 the purpose of this revision? Is it to make it easier to write client
 applications using SQLite for internal storage? Or to make the C client
 code 'a generic API' for connecting to both MySQL (of all flavors) and
 SQLite? Is the the code/files that that were added different from offical
 SQLite downloads from http://www.sqlite.org/? I am not able to find any
 documentation anywhere.  Also not a blog or whatever either. There must be
 some reason to add sqlite3 code?!



 3)
 This seems to be the latest revision:

 https://bazaar.launchpad.net/~maria-captains/mariadb-native-client/trunk/revision/81
 Added dyamic column api; Added character set conversion
 ('dyamic' is misspelled BTW!)

 Won't we need some documentation here? The claim that MariaDB's connector
 has exactly the same API as the MySQL Connector/C for MySQL 5.5 (
 https://kb.askmonty.org/en/mariadb-client-library-for-c/) cannot be true
 now as it adds funtionalities for managing MariaDB ' dymamic column waht
 oracle's API has not? The API from Oracle's library is now a *subset* or
 MariaDB API (or MariaDB's is a *superset* or Oracle). So much I can figure
 out, but should I need to code with it I would need description of
 functions' syntax, expected results and error listings.

 Also I am not able to figure out what the character set conversion
 referred to is doing and why it was added.


 4)
 Why does the changelog here
 https://kb.askmonty.org/en/mariadb-client-library-for-c-100-changelog/stop at 
 revision 77?


 -- Peter Laursen
 -- Webyog

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

[Maria-developers] Some clarifications requested for C client

[Peter Laursen]

This is probably for Georg Richter (and/or @Wlad). I have a few qeustion!


1)
https://bazaar.launchpad.net/~maria-captains/mariadb-native-client/trunk/revision/80
Fix for CONC-44: LOAD DATA INFILE can't open utf16le encoded filenames
But we we can stil not specify UTF16LE as the CHARSET, I think?

Say I have a file *named* ÄÜÑБГД.csv.  (both Western special characters
and cyrillic characters in the file name). This file I  will be able to
read now (using revision 80), right?

But if file *content* is this single line (one row, two columns)

ÄÜÑ,БГД

and if it is encoded as 'Windows Unicode'/utf16le I still will need to
recode the file to utf8 before executing it with LOAD DATA (as UTF16LE
still cannot be specified for CHARSET in LOAD DATA), right?

Please confirm that I understand this!


2)
https://bazaar.launchpad.net/~maria-captains/mariadb-native-client/trunk/revision/32
Added support for embedded (sqlite).
This happened by beginning of this year but I just noticed now.

Now what can we actually do with SQLite and the MariaDB C-API and what we
the purpose of this revision? Is it to make it easier to write client
applications using SQLite for internal storage? Or to make the C client
code 'a generic API' for connecting to both MySQL (of all flavors) and
SQLite? Is the the code/files that that were added different from offical
SQLite downloads from http://www.sqlite.org/? I am not able to find any
documentation anywhere.  Also not a blog or whatever either. There must be
some reason to add sqlite3 code?!



3)
This seems to be the latest revision:
https://bazaar.launchpad.net/~maria-captains/mariadb-native-client/trunk/revision/81
Added dyamic column api; Added character set conversion
('dyamic' is misspelled BTW!)

Won't we need some documentation here? The claim that MariaDB's connector
has exactly the same API as the MySQL Connector/C for MySQL 5.5 (
https://kb.askmonty.org/en/mariadb-client-library-for-c/) cannot be true
now as it adds funtionalities for managing MariaDB ' dymamic column waht
oracle's API has not? The API from Oracle's library is now a *subset* or
MariaDB API (or MariaDB's is a *superset* or Oracle). So much I can figure
out, but should I need to code with it I would need description of
functions' syntax, expected results and error listings.

Also I am not able to figure out what the character set conversion
referred to is doing and why it was added.


4)
Why does the changelog here
https://kb.askmonty.org/en/mariadb-client-library-for-c-100-changelog/ stop
at revision 77?


-- Peter Laursen
-- Webyog
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Some clarifications requested for C client

[Peter Laursen]

And also .. the revisions listing at Launchpad (
http://bazaar.launchpad.net/~georghd/mariadb-native-client/1.3/changes/)
stops at revision 32, it seems. If it is not maintained I think it is
better to delete/truncate it. Besides I am also surprised to se the version
listed as 1.3.  But maybe I don't understand how to navigate Launchpad!

-- Peter


On Sun, Aug 25, 2013 at 3:25 PM, Peter Laursen peter_laur...@webyog.comwrote:

 This is probably for Georg Richter (and/or @Wlad). I have a few qeustion!


 1)

 https://bazaar.launchpad.net/~maria-captains/mariadb-native-client/trunk/revision/80
 Fix for CONC-44: LOAD DATA INFILE can't open utf16le encoded filenames
 But we we can stil not specify UTF16LE as the CHARSET, I think?

 Say I have a file *named* ÄÜÑБГД.csv.  (both Western special characters
 and cyrillic characters in the file name). This file I  will be able to
 read now (using revision 80), right?

 But if file *content* is this single line (one row, two columns)

 ÄÜÑ,БГД

 and if it is encoded as 'Windows Unicode'/utf16le I still will need to
 recode the file to utf8 before executing it with LOAD DATA (as UTF16LE
 still cannot be specified for CHARSET in LOAD DATA), right?

 Please confirm that I understand this!


 2)

 https://bazaar.launchpad.net/~maria-captains/mariadb-native-client/trunk/revision/32
 Added support for embedded (sqlite).
 This happened by beginning of this year but I just noticed now.

 Now what can we actually do with SQLite and the MariaDB C-API and what we
 the purpose of this revision? Is it to make it easier to write client
 applications using SQLite for internal storage? Or to make the C client
 code 'a generic API' for connecting to both MySQL (of all flavors) and
 SQLite? Is the the code/files that that were added different from offical
 SQLite downloads from http://www.sqlite.org/? I am not able to find any
 documentation anywhere.  Also not a blog or whatever either. There must be
 some reason to add sqlite3 code?!



 3)
 This seems to be the latest revision:

 https://bazaar.launchpad.net/~maria-captains/mariadb-native-client/trunk/revision/81
 Added dyamic column api; Added character set conversion
 ('dyamic' is misspelled BTW!)

 Won't we need some documentation here? The claim that MariaDB's connector
 has exactly the same API as the MySQL Connector/C for MySQL 5.5 (
 https://kb.askmonty.org/en/mariadb-client-library-for-c/) cannot be true
 now as it adds funtionalities for managing MariaDB ' dymamic column waht
 oracle's API has not? The API from Oracle's library is now a *subset* or
 MariaDB API (or MariaDB's is a *superset* or Oracle). So much I can figure
 out, but should I need to code with it I would need description of
 functions' syntax, expected results and error listings.

 Also I am not able to figure out what the character set conversion
 referred to is doing and why it was added.


 4)
 Why does the changelog here
 https://kb.askmonty.org/en/mariadb-client-library-for-c-100-changelog/stop at 
 revision 77?


 -- Peter Laursen
 -- Webyog

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Can't sign up to JIRA

[Peter Laursen]

I just want to add that I find JIRA very tedious to use. If I have not used
it for a while, I cannot authenticate and will have to go through the reset
password procedure again. And the interface for this is confusing.
 Besides, does password expire after a week? It looks like it.

-- Peter


On Wed, Aug 21, 2013 at 5:16 AM, Kouhei Sutou k...@clear-code.com wrote:

 Hi,

 I tried to sign up to JIRA(*) for submitting a bug report.

 (*) https://mariadb.atlassian.net/secure/Signup!default.jspa

 But I couldn't sign up because I couldn't get captcha image.
 I used Chromium 28.0.1500.95 Debian jessie/sid (213514)
 and Iceweasel 7.0.8 on Debian GNU/Linux sid as Web
 browsers. I got the same result with these Web browsers.

 I checked captcha image response by Chromium's developer
 tool. https://mariadb.atlassian.net/captcha returns 500
 Internal Server Error with the following body. Could you
 confirm it?

 
 We had some technical problems during your last operation.
 We deeply apologize for that :(

 If you need further assistance, please:

 Expand the section Technical details below
 Copy the content from it
 Send it to your JIRA Administrator
 Technical details

 Cause

 Referer URL: https://mariadb.atlassian.net/secure/Signup!default.jspa

 java.lang.NoClassDefFoundError: Could not initialize class
 com.atlassian.jira.servlet.NoOpImageCaptchaService
 java.lang.NoClassDefFoundError: Could not initialize class
 com.atlassian.jira.servlet.NoOpImageCaptchaService
   at
 com.atlassian.jira.servlet.NoOpCaptchaServiceImpl.getImageCaptchaService(NoOpCaptchaServiceImpl.java:14)
   at
 com.atlassian.jira.servlet.JiraCaptchaServlet.doGet(JiraCaptchaServlet.java:50)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
   at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at
 com.atlassian.jira.web.filters.steps.ChainedFilterStepRunner.doFilter(ChainedFilterStepRunner.java:87)
   at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
   at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at
 com.atlassian.jira.web.filters.XContentTypeOptionsNoSniffFilter.doFilter(XContentTypeOptionsNoSniffFilter.java:22)
   at
 com.atlassian.core.filters.AbstractHttpFilter.doFilter(AbstractHttpFilter.java:31)
   at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
   at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at
 com.atlassian.core.filters.HeaderSanitisingFilter.doFilter(HeaderSanitisingFilter.java:44)
   at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
   at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at
 com.atlassian.plugin.servlet.filter.IteratingFilterChain.doFilter(IteratingFilterChain.java:46)
   at
 com.atlassian.plugin.servlet.filter.DelegatingPluginFilter$1.doFilter(DelegatingPluginFilter.java:66)
   at
 com.atlassian.jira.tzdetect.IncludeResourcesFilter.doFilter(IncludeResourcesFilter.java:39)
   at
 com.atlassian.plugin.servlet.filter.DelegatingPluginFilter.doFilter(DelegatingPluginFilter.java:74)
   at
 com.atlassian.plugin.servlet.filter.IteratingFilterChain.doFilter(IteratingFilterChain.java:42)
   at
 com.atlassian.plugin.servlet.filter.DelegatingPluginFilter$1.doFilter(DelegatingPluginFilter.java:66)
   at
 com.atlassian.jira.baseurl.IncludeResourcesFilter.doFilter(IncludeResourcesFilter.java:38)
   at
 com.atlassian.core.filters.AbstractHttpFilter.doFilter(AbstractHttpFilter.java:31)
   at
 com.atlassian.plugin.servlet.filter.DelegatingPluginFilter.doFilter(DelegatingPluginFilter.java:74)
   at
 com.atlassian.plugin.servlet.filter.IteratingFilterChain.doFilter(IteratingFilterChain.java:42)
   at
 com.atlassian.plugin.servlet.filter.DelegatingPluginFilter$1.doFilter(DelegatingPluginFilter.java:66)
   at
 com.atlassian.applinks.core.rest.context.ContextFilter.doFilter(ContextFilter.java:25)
   at
 com.atlassian.plugin.servlet.filter.DelegatingPluginFilter.doFilter(DelegatingPluginFilter.java:74)
   at
 com.atlassian.plugin.servlet.filter.IteratingFilterChain.doFilter(IteratingFilterChain.java:42)
   at
 com.atlassian.plugin.servlet.filter.DelegatingPluginFilter$1.doFilter(DelegatingPluginFilter.java:66)
   at
 com.atlassian.mywork.client.filter.ServingRequestsFilter.doFilter(ServingRequestsFilter.java:37)
   at
 com.atlassian.plugin.servlet.filter.DelegatingPluginFilter.doFilter(DelegatingPluginFilter.java:74)
   at
 com.atlassian.plugin.servlet.filter.IteratingFilterChain.doFilter(IteratingFilterChain.java:42)
   at
 

Re: [Maria-developers] Can there be a better storage engine API?

[Peter Laursen]

I think PBXT is the best example till now that the SE API actually works.
 Paul, who created it, also was not grown in MySQL but he managed to figure
out good enough to write a complete transactional general-purpose storage
engine.

It did not quite reach GA level. But I don't think the API is to blame. I
think Paul needed to turn his efforts towards activities earning him a
living (and maybe also he realized that after Oracle's aquisition of Sun
that there were no chances that PBXT would be aquired).

But that does not exclude that better and more detailed docs as well as
'guides' would be useful.

-- Peter Laursen



On Mon, Aug 19, 2013 at 5:36 PM, MARK CALLAGHAN mdcal...@gmail.com wrote:

 Thanks for your response.

 On Fri, Aug 16, 2013 at 11:23 AM, Zardosht Kasheff zardo...@gmail.comwrote:

 I've worked on the TokuDB storage engine for quite a while now. I have
 had many experiences over the years, so I guess it's hard to know
 where to begin. I guess I will start small, and if the conversation
 evolves, I can contribute more thoughts. I think the current API is
 really good, as evidenced by the fact that many storage engines have
 used it to plug into MySQL. The two areas that I see we can really
 benefit from are the following:


 Many were written in the long-ago past. Besides TokuDB how many new
 storage engines have reached GA in the past decade? I worked on a custom
 storage engine and I am sure others have done the same, but there hasn't
 been much innovation in the public. Aria is also GA, but that was written
 by people who know and wrote parts of the API, so it isn't a sign that the
 API is something people want to use.

 Was TokuMX easier to implement than TokuDB?

 --
 Mark Callaghan
 mdcal...@gmail.com

 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] COT() function

[Peter Laursen]

I just checked in (Oracle) MySQL 5.5.32 and 5.6.13.

SELECT COT(0)
-- returns
Error CODE: 1690
DOUBLE VALUE IS OUT of RANGE IN 'cot(0)'


So this change in behaviour has its origin in (Oracle) MySQL 5.5.


On Thu, Aug 1, 2013 at 9:56 PM, Ian Gilfillan launch...@greenman.co.zawrote:

 Hi

 SELECT COT(0) returns:

 ERROR 1690 (22003): DOUBLE value is out of range in 'cot(0)'

 in both MariaDB 10 and 5.5, but in MySQL 5.1 it returns NULL.

 I can't find a changelog reference to this, but I see it's still
 documented as returning NULL in MySQL 5.5 (I don't have this to test on).
 Is this a MariaDB-specific change? When did this change in behaviour happen?

 thanks,
 ian

 __**_
 Mailing list: 
 https://launchpad.net/~maria-**developershttps://launchpad.net/~maria-developers
 Post to : 
 maria-developers@lists.**launchpad.netmaria-developers@lists.launchpad.net
 Unsubscribe : 
 https://launchpad.net/~maria-**developershttps://launchpad.net/~maria-developers
 More help   : 
 https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] RFC: Pausing a query thread

[Peter Laursen]

I think it is a known issue wiht 'hsared hosting' . Any user can fire a
query killing the server (for example causing excessive memory load ude to
a cartesian join on huge tables, or CPU due a a routine entering an
infinite loop. It can be both due to user's lack of skills og even be a
malicious attack/teeny experiment.

I have always wondered how hosting companies handled that. MySQL does not
provide any mechanism for 'isolating server resources per user or per
database or whatever'. Still MySQL has been the most popular choice of
database for such hosting companies for a decade. I think that in extreme
cases most 'shared hosting will kill such query and sometimes warn users if
it repeats frequently.  But cases can alos be valid. Some queries require
lot of memory or CPU or whatever.

I think Marian's request for an admin option to pause a specific query is a
reasonable workaround.  But only that.  A priority setting by the server
for queries|users|databases and automatic allocation of resources
accordingly would be a better option.

From one that used 'shared hosting' quite a lot many years ago - but who
did not for 6-7 years at least.

Peter
Webyog


On Mon, Jun 24, 2013 at 5:31 PM, Marian Marinov m...@yuhu.biz wrote:

 I have seen the problems with both MyISAM, InnoDB and even with memory
 storage.

 I want to stop the executing thread instead of implementing the change in
 the storage engines.

 Unfortunately hosting companies can not change the software of their
 clients and also don't have the manpower to do that.

 So a solution for them would only be if it is possible to pause the
 executing thread until the server calms down.
 It is a unique situation where general replies as Fix your database
 design, Optimize your query or Upgrade to the next version are not
 possible. It is impossible to fix the enormous amount of software that they
 are hosting.

 Marian

 On 06/24/2013 03:48 PM, Roberto Spadim wrote:

 hum, it's a innodb table? a myisam? what are you talking about high
 resource? locked tables? high write/read ?


 2013/6/24 Marian Marinov m...@yuhu.biz mailto:m...@yuhu.biz

 Hi guys,

 I work with hosting companies and all of my clients have the same
 irritating problem, one query taking a lot of time
 to finish and consuming a lot of resources.

 So I have solved the same issue but with processes on the machine by
 simply pausing(kill -STOP) these processes when
 the load is high and continuing(kill -CONT) them when the server load
 goes down.

 I want to implement the same logic within MariaDB, so I can STOP/CONT
 the thread that is executing this query.

 My idea is to implement this in the 'KILL query_id' function, so it
 will accept one more argument, which will be
 either STOP or CONT. If the parameter is not present, the default
 behavior should remain.

 What do you think about my approach?

 Marian

 __**___
 Mailing list: 
 https://launchpad.net/~maria-_**_developershttps://launchpad.net/~maria-__developers
 https://launchpad.net/~maria-**developershttps://launchpad.net/~maria-developers
 
 Post to : 
 maria-developers@lists.__launc**hpad.nethttp://launchpad.netmailto:
 maria-developers@**lists.launchpad.netmaria-developers@lists.launchpad.net
 
 Unsubscribe : 
 https://launchpad.net/~maria-_**_developershttps://launchpad.net/~maria-__developers
 https://launchpad.net/~maria-**developershttps://launchpad.net/~maria-developers
 
 More help   : 
 https://help.launchpad.net/__**ListHelphttps://help.launchpad.net/__ListHelp
 https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp
 




 --
 Roberto Spadim
 SPAEmpresarial



 __**_
 Mailing list: 
 https://launchpad.net/~maria-**developershttps://launchpad.net/~maria-developers
 Post to : 
 maria-developers@lists.**launchpad.netmaria-developers@lists.launchpad.net
 Unsubscribe : 
 https://launchpad.net/~maria-**developershttps://launchpad.net/~maria-developers
 More help   : 
 https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] RFC: Pausing a query thread

[Peter Laursen]

Why not take a more daring approach - implement 'priorities' in
processlist?
SET PRIORITY = high|medium|low [or 1..9]  FOR processlist.ID=xx;

I realize that this is not a trivial task, and obviously it requires so
much change in server architecture that it is not a solution for Marian
here-and-now.

@Marian BTW (as you probably know the answer): what do hosting companies
offering 2.95 $-per-month 'web hotel' solutions do where hundreds or
thousands of users/customers share a MySQL server and one user repeatedly
executes idiotic queres from home-grown applications resulting in starving
of the server and thus effectively causing denial-of-service for other
users/customers? I was always surprised that they could manage it with
MySQL, actually!

-- Peter


On Mon, Jun 24, 2013 at 9:50 PM, Marian Marinov m...@yuhu.biz wrote:

 Hi Roberto,
 MDEV-4623 is does exactly what I want in a different manner.

 I have a similar thing as MDEV-4427 written as MySQL plugin. Unfortunately
 this have one very big problem. It sometimes breaks tables. I have seen
 even InnoDB tables broken by this type of intervention :( I can't reproduce
 it very easy for InnoDB, but for MyISAM it should be pretty easy.
 Also killing query, even one that takes a lot of resources may result in a
 loss of data, which in turn says, that the service is bad.

 My opinion is, we should either accept a query and try to execute it while
 preventing resource starvation or we should deny it. It is very bad to
 accept it and then kill it in the middle of its work.
 This is a DataBase, it should either accept data or not.

 Marian

 On 06/24/2013 08:15 PM, Roberto Spadim wrote:

 hi marian, could you see MDEV-4623 and MDEV-4427, and tell me if that
 could help you?

 MDEV-4623 
 https://mariadb.atlassian.**net/browse/MDEV-4623https://mariadb.atlassian.net/browse/MDEV-4623
 - 
 https://mariadb.atlassian.net/**browse/MDEV-4623https://mariadb.atlassian.net/browse/MDEV-4623-
 lock/unlock connection
 MDEV-4427 
 https://mariadb.atlassian.**net/browse/MDEV-4427https://mariadb.atlassian.net/browse/MDEV-4427
 - 
 https://mariadb.atlassian.net/**browse/MDEV-4427https://mariadb.atlassian.net/browse/MDEV-4427-
  twitter
 like patch (this one is to kill a query, but after MDEV-4623 we could use
 lock connection)



 __**_
 Mailing list: 
 https://launchpad.net/~maria-**developershttps://launchpad.net/~maria-developers
 Post to : 
 maria-developers@lists.**launchpad.netmaria-developers@lists.launchpad.net
 Unsubscribe : 
 https://launchpad.net/~maria-**developershttps://launchpad.net/~maria-developers
 More help   : 
 https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] RFC: Pausing a query thread

[Peter Laursen]

what this should do?.  Processlist would then have one more column
('PRIORITY*). And the value of that column is the priority with what the OS
executes this paricular thread (forever in the lifetime of the thread or
for the time of current query only - could be one more parameter). But my
system knowledge is not deep enough to decide if the idea is feasible wtit
reasonable effort. I actually don't know if priorities are only available
for processes and not threads in various OS'es. If the control should be
implemented inside the server without calling OS routines, I realize it is
a huge project.

Also my proposed syntax should more be seen as 'pseudo code' than an actual
implementation. But SET PRIORITY [FOR THIS] could make sense if it could
also be executed from clients/scripts running with sufficient privileges.
You may want to SET PRIORITY *low* (don't let this thread have any impact
on other threads) - but also maybe sometimes to set it *high* in some
cases (this is more important than anything else and it does not matter if
other threads suffer).


If you can afford a server instance (virtual or not) per customer there are
many posibilities. But that is not Marian's environment I think. If it was,
she would not have found the solution inside MySQL. I understand that this
is about management of traditional 'shared hosting', where users/customers
that are completely unrelated and have no knowledge of each others share
access to a MySQL server - only managed by different user accounts and
their privileges.


-- Peter


On Mon, Jun 24, 2013 at 10:56 PM, Roberto Spadim robe...@spadim.com.brwrote:

 hi Peter, i was helping some guys in a datacenter here in brazil and they
 implement server hosting via virtual machines, in other words, they have a
 very big linux cluster and many virtual machines with memory/cpu
 restrictions, maybe that's the solution they give... in each virtual
 machine they run a 'small server', it's a very 'expensive' solution, but
 works... a cheaper one could be a per process restriction via variables
 tunes / os restrictions

 there's some others mysql patchs (github lauchpad others) that limit mysql
 resources, but i didn't used


 ---
 getting back to your idea: SET PRIOTITY =  FOR processlist.id=
 what this should do? change 'nice' value of linux pid? it can help, but i
 tryed this some times and when problem is disk i/o limit it don't 'solve'
 the problem, just help

 i see a better solution using the MDEV-4623 that i told, and this others
 MDEVs (MDEV-4615 https://mariadb.atlassian.net/browse/MDEV-4615 -
 vertical partitioning, 
 MDEV-3932https://mariadb.atlassian.net/browse/MDEV-3932 -
 mysql 5.6 merge) with vetical/horizontal partitioning and partition lock
 prunes

 with vertical/horizontal partitioning + partition lock prunes, we can
 change a myisam table with table lock level, to a myisam table with
 'partition lock' level, and implement a good partitioning that help us to
 minimize the lock contention, and after we can change query cache to prune
 partitions too, giving a better query cache hit rate 
 (MDEV-4676https://mariadb.atlassian.net/browse/MDEV-4676
 )

 any other idea? maybe after this mdevs an script could 'optimize' server
 'online' reading query cache queries removing some queries, reading
 processlist and locking/unlocking some process and any other feature

 my ideas was added in mariadb JIRA but i don't know if this solve your
 problem and when someone will start development, i don't know many things
 about mariadb source code, and i can't develop it (not yet =], but maybe in
 future i can), if you want to vote that mdev we can have a better rank
 position in JIRA and maybe someone give more priority to this and help us
 developing

 any other ideas? i have the same problem for many queries, but in my case
 i can change source code of some projects, others projects i just tell
 developers to rewrite queries and optimize to better performace

 sorry my english errors that's not my main language.

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Uninstalling MariaDB 5.2 does not remove everything.

[Peter Laursen]

An example of and more:


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-21-2656319016-1596626723-3555400582-1000\Components\7748B6BD67D549653B9F33A6BDE97A51]
3DC5D27742DD8714EA85F2707228779F=C:\\Program Files\\MariaDB
5.2\\include\\mysql.h


A C header file added to my registry when installing a binary?


-- Peter


On Sat, Jun 22, 2013 at 6:19 PM, Peter Laursen peter_laur...@webyog.comwrote:

 refresh does not work. clsong control panel and opening again also not.
 deleteing the registry keys



 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\3DC5D27742DD8714EA85F2707228779F]
 ProductName=MariaDB 5.2 (x64)
 PackageCode=B1AC285B4BC88BC4384EB09D8858B043
 Language=dword:0409
 Version=dword:05020005
 Assignment=dword:
 AdvertiseFlags=dword:0184
 InstanceType=dword:
 AuthorizedLUAApp=dword:
 DeploymentFlags=dword:0003
 Clients=hex(7):3a,00,00,00,00,00


 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\3DC5D27742DD8714EA85F2707228779F\SourceList]
 PackageName=mariadb-5.2.5-winx64.msi

 LastUsedSource=hex(2):6e,00,3b,00,31,00,3b,00,43,00,3a,00,5c,00,55,00,73,00,\

 65,00,72,00,73,00,5c,00,50,00,65,00,74,00,65,00,72,00,5c,00,44,00,65,00,73,\
 00,6b,00,74,00,6f,00,70,00,5c,00,00,00


 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\3DC5D27742DD8714EA85F2707228779F\SourceList\Media]
 1=;


 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\3DC5D27742DD8714EA85F2707228779F\SourceList\Net]

 1=hex(2):43,00,3a,00,5c,00,55,00,73,00,65,00,72,00,73,00,5c,00,50,00,65,00,\

 74,00,65,00,72,00,5c,00,44,00,65,00,73,00,6b,00,74,00,6f,00,70,00,5c,00,00,\
 00

 [HKEY_CURRENT_USER\Software\MariaDB 5.2 (x64)]

 [HKEY_CURRENT_USER\Software\MariaDB 5.2 (x64)\Uninstall]
 shortcuts=1
 shortcuts.commandline=1
 shortcuts.commandprompt.db=1


 .. not either. At least not as long as system is not restarted.


 Running an old version of 'jv16' (2010 version) registry cleaner does not
 remove it either.


 BTW: what a horrible lot of garbage that is left over from MariaDB 5.2 in
 registry!  Entries for every charset, script and executable - and more.
  Not a big issue (lots of programs has this problem and Windows handles it,
 but just FYI!)


 -- Peter


 On Sat, Jun 22, 2013 at 6:10 PM, Vladislav Vaintroub 
 w...@montyprogram.com wrote:

 I believe you just need to refresh this “Control Panel\Programs\Programs
 and Features” window  with F5.   I would guess that you had 2 such
 windows open, before uninstall, and the window you have open contains old
 state prior to  deinstallation, and this state needs to be refreshed ,
 with F5

 ** **

 *From:* Maria-developers [mailto:maria-developers-bounces+wlad=
 montyprogram@lists.launchpad.net] *On Behalf Of *Peter Laursen
 *Sent:* Samstag, 22. Juni 2013 17:18
 *To:* Maria Developers
 *Subject:* [Maria-developers] Uninstalling MariaDB 5.2 does not remove
 everything.

 ** **

 ** **

 For @wlad I guess:

 ** **

 After uninstalling MariaDB 5.2.on Win7/64 some (don't remember which
 minor version),  it remains in the list of installed programs in Control
 Panel .. Programs.

 ** **

 Trying to uninstall displays this dialog (translates to This action is
 only valid for programs currently installed).

 ** **

 I did not try if rebooting system would remove the item from the list. It
 may also have been fixed in the installer since the 5.2 release I installed.
 

 ** **

 ** **

 -- Peter 



___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Uninstalling MariaDB 5.2 does not remove everything.

[Peter Laursen]

 that the uninstall con in CÅ .. Programs did
not go with the uninstallation.

Also I may have had older 5.2 versions before 5.2.10 (the last 5.2 I had)
installed and some of the garbage in registry may have come from such older
version(s). I also found a little left-over garbage from 5.3 (that was
uninstalled a few months ago), but only few percent of what was left over
from 5.2.


All this was mainly posted FYI, BTW. I can handle such issues on my system.
But you should know what to reply to users reporting this in the future -
if it should happen again.


-- Peter



On Sat, Jun 22, 2013 at 6:33 PM, Vladislav Vaintroub
w...@montyprogram.comwrote:

 Peter,

 Whatever it is on your machine (I cannot reproduce it on anything), we
 rely on MSI to work correctly.  Except MariaDB service entry , we do not
 create any registry entries ourselves, we rely on MSI to create and to
 cleanup correctly when it is finished.   And, on every machine I touched
 so far, it has worked correctly. But If this does not  work, on whatever
 reasons, the correct address to complain is Microsoft.

 ** **

 ** **

 *From:* Peter Laursen [mailto:peter_laur...@webyog.com]
 *Sent:* Samstag, 22. Juni 2013 18:20
 *To:* Vladislav Vaintroub
 *Cc:* Maria Developers
 *Subject:* Re: [Maria-developers] Uninstalling MariaDB 5.2 does not
 remove everything.

 ** **

 refresh does not work. clsong control panel and opening again also not.
 deleteing the registry keys

 ** **

 ** **


 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\3DC5D27742DD8714EA85F2707228779F]
 ProductName=MariaDB 5.2 (x64)
 PackageCode=B1AC285B4BC88BC4384EB09D8858B043
 Language=dword:0409
 Version=dword:05020005
 Assignment=dword:
 AdvertiseFlags=dword:0184
 InstanceType=dword:
 AuthorizedLUAApp=dword:
 DeploymentFlags=dword:0003
 Clients=hex(7):3a,00,00,00,00,00


 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\3DC5D27742DD8714EA85F2707228779F\SourceList]
 PackageName=mariadb-5.2.5-winx64.msi

 LastUsedSource=hex(2):6e,00,3b,00,31,00,3b,00,43,00,3a,00,5c,00,55,00,73,00,\

 65,00,72,00,73,00,5c,00,50,00,65,00,74,00,65,00,72,00,5c,00,44,00,65,00,73,\
 00,6b,00,74,00,6f,00,70,00,5c,00,00,00


 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\3DC5D27742DD8714EA85F2707228779F\SourceList\Media]
 1=;


 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\3DC5D27742DD8714EA85F2707228779F\SourceList\Net]

 1=hex(2):43,00,3a,00,5c,00,55,00,73,00,65,00,72,00,73,00,5c,00,50,00,65,00,\

 74,00,65,00,72,00,5c,00,44,00,65,00,73,00,6b,00,74,00,6f,00,70,00,5c,00,00,\
 00

 ** **

 [HKEY_CURRENT_USER\Software\MariaDB 5.2 (x64)]

 [HKEY_CURRENT_USER\Software\MariaDB 5.2 (x64)\Uninstall]
 shortcuts=1
 shortcuts.commandline=1
 shortcuts.commandprompt.db=1

 ** **

 ** **

 .. not either. At least not as long as system is not restarted.

 ** **

 ** **

 Running an old version of 'jv16' (2010 version) registry cleaner does not
 remove it either. 

 ** **

 ** **

 BTW: what a horrible lot of garbage that is left over from MariaDB 5.2 in
 registry!  Entries for every charset, script and executable - and more.
  Not a big issue (lots of programs has this problem and Windows handles it,
 but just FYI!)

 ** **

 ** **

 -- Peter

 ** **

 On Sat, Jun 22, 2013 at 6:10 PM, Vladislav Vaintroub 
 w...@montyprogram.com wrote:

 I believe you just need to refresh this “Control Panel\Programs\Programs
 and Features” window  with F5.   I would guess that you had 2 such windows
 open, before uninstall, and the window you have open contains old  state
 prior to  deinstallation, and this state needs to be refreshed , with F5**
 **

  

 *From:* Maria-developers [mailto:maria-developers-bounces+wlad=
 montyprogram@lists.launchpad.net] *On Behalf Of *Peter Laursen
 *Sent:* Samstag, 22. Juni 2013 17:18
 *To:* Maria Developers
 *Subject:* [Maria-developers] Uninstalling MariaDB 5.2 does not remove
 everything.

  

  

 For @wlad I guess:

  

 After uninstalling MariaDB 5.2.on Win7/64 some (don't remember which minor
 version),  it remains in the list of installed programs in Control Panel ..
 Programs.

  

 Trying to uninstall displays this dialog (translates to This action is
 only valid for programs currently installed).

  

 I did not try if rebooting system would remove the item from the list. It
 may also have been fixed in the installer since the 5.2 release I installed.
 

  

  

 -- Peter 

 ** **

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] [Maria-discuss] Clear-text plugin

[Peter Laursen]

no support for dlopen() .  How does this apply to Windows clients?  We
always build first on Windows and once we have no errors of any kind we
build on Linux if the application exists for that platform (what MONyog
does and SQLyog does not) and fix what issues may occur there.

This issue has occurred with SQLyog (and as such for a Windows client).

I am not coder/developer myself, but on Windows I think we have no other
option than statically linking? We could of could compile the API as a
.dll, but we don't (because we had a lot of problems with it earlier).

-- Peter


On Thu, Jun 6, 2013 at 3:25 PM, Sergei Golubchik s...@mariadb.org wrote:

 Hi, Peter!

 On Jun 04, Peter Laursen wrote:
  We have the same problem.  We cannot test either. But we have a few user
  reports.  We will discuss what we can do.
 
  Is there any parameter or compile-time option we should be aware of? Any
  specific documentation somewhere? Anything?

 Not really. If the cleartext plugin is built and installed, it'll be
 used when the server requests it.

 I've just checked that this plugin is present both in rpm and deb
 packages. I didn't check binary tarballs, but it should be there too.

 So, there's nothing to configure at run-time or compile-time, everything
 should work automatically and transparently.

 Hmm, unless you build a completely static client library with no support
 for dlopen().

 Regards,
 Sergei

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

[Maria-developers] Clear-text plugin

[Peter Laursen]

This is a continuation of https://mariadb.atlassian.net/browse/CONC-25. We
requested support for the clear-text plugin (or a workaround of any kind)
that would allow a client compiled with the MariaDB connector to use PAM
authentication with MySQL Enterprise servers from Oracle.

I will not dispute Sergei's opinions about Oracle's implementation.  But I
believe it misses the point. The question is if the MariaDB connector
should be a replacement for the C-IPA from Oracle. And the question is
nothing else than that. Not the quality of solutions bundled with
Enterprise servers from Oracle.

I would like to hear opinions not only from 'core developers' like Sergei,
but also from wider circles in MariaDB organization (management, marketing)
as well as the user community.

For us the problem is like this: We introduced support for the clear-text
plugin in SQLyog 11.1.  In 11.12 beta2 we replaced Oracles connector with
MariaDB (and had to removed it again). We had a few crashes and memory
leaks with mariaDB Connector but that is getting in control now (ther were
bugs in both the API and in oru code).  We probably could patch the MariaDB
code without much problems to support the full-text plugin - but we don't
have a MySQL Enterprise server to test with and we cannot release without
proper testing.

We have already started getting complaints from users/customers about that
what we introduced in 11.1 has been removed in current development tree.
 It seems that we have quite a lot of customers using Oracle's Enterprise
servers wiht Oracle's PAM authentication.

A solution/workaround would very much be appreciated.


Regards

Peter Laursen
Webyog
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] [Maria-discuss] Clear-text plugin

[Peter Laursen]

For clarity: a 'dummy' parameter doing nothing does not solve our problem.
We actually want to build clients that can (also) connect to Oracle MySQL
Enterprise servers configured to make use of Oracle's PAM implementation.

-- Peter


On Tue, Jun 4, 2013 at 11:05 AM, Peter Laursen peter_laur...@webyog.comwrote:

 yes .. in the Connector/C.  We use C/C++ for both SQLyog and MONyog.

 -- Peter


 On Tue, Jun 4, 2013 at 10:17 AM, Sergei Golubchik s...@mariadb.orgwrote:

 Hi, Peter!

 On Jun 04, Peter Laursen wrote:
  This is a continuation of
  https://mariadb.atlassian.net/browse/CONC-25. We requested support for
  the clear-text plugin (or a workaround of any kind) that would allow a
  client compiled with the MariaDB connector to use PAM authentication
  with MySQL Enterprise servers from Oracle.

 Another related issue is https://mariadb.atlassian.net/browse/MDEV-4574
 which should be fixed in 5.5.32, next 5.5 release.

 But you, probably, want it in Connector/C, don't you?

 Regards,
 Sergei



___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] [Maria-discuss] Clear-text plugin

[Peter Laursen]

We have the same problem.  We cannot test either. But we have a few user
reports.  We will discuss what we can do.

Is there any parameter or compile-time option we should be aware of? Any
specific documentation somewhere? Anything?

-- Peter


On Tue, Jun 4, 2013 at 2:19 PM, Sergei Golubchik s...@mariadb.org wrote:

 Hi, Peter!

 On Jun 04, Peter Laursen wrote:
  For clarity: a 'dummy' parameter doing nothing does not solve our
  problem.  We actually want to build clients that can (also) connect to
  Oracle MySQL Enterprise servers configured to make use of Oracle's PAM
  implementation.

 We build and distribute a cleartext plugin. And it can be used if the
 server requests. In a sense, in MariaDB a cleartext plugin is always
 enabled. So a dummy option is needed only to restore the binary protocol
 compatibility. That's my understanding, at least, but I don't have
 Oracle's PAM plugin, so I cannot test it.

 But if you have verified that your client with our C connector can not
 connect to Oracle MySQL Enterprise server with the Oracle's PAM
 implementation - please submit a bug report, and we will fix it.

 Regards,
 Sergei


___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] [Maria-discuss] Json Explain

[Peter Laursen]

I do not see why this should be a concern for the optimizer team.

The output from EXPLAIN (in any format) does not affect optimizer's
operation but only provides information of *optimizer result*. The format
chosen is (?) applied is *after* not *before* or *during* the optimization
process.

TRADITIONAL EXPLAIN returns the result as an **array**.  JSON EXPLAIN
returns the result as a single (Json-formatted) **string** (not unlike SHOW
ENGINE INNODB STATUS, btw).  But both should have exactly the same
information - and if they don't it is a bug with JSON EXPLAIN in MySQL 5.6
IMO.

But as I am not well-versed in server internals, I could have
ovelooked/misunderstood something, of course.

-- Peter

On Fri, Sep 28, 2012 at 5:18 PM, Peter Laursen peter_laur...@webyog.comwrote:

 @wlad is completely right!

 Workbench introduced a Visual Explain based on JSON EXPLAIN as Blogged
 here: http://www.arubin.org/blog/2012/09/26/mysql-visual-explain/

 The very reason why JSON EXPLAIN was introduced in MySQL 5.6 could be that
 Oracle develops the server and tools (WB, Enterprirse Monitor primarily) in
 parallel.  Some recently introduced features in the server could be
 introduced for the primary reason that they should be 'exploited' by MEM
 and/or WB.  JSON EXPLAIN is one. Another example is the Performance_Schema
 table introduced in 5.6.6 (I don't remember the table name)  that records
 an 'aggregated summary' of queries' performance. Actually this table has
 about the same information as what MONyog 'Query Analyzer' module displays
 in its most simple display mode (but MONyog can be 'drilled down' to a more
 detailed view).

 So Oracle *thinks* the server and their most important tools *as a whole*,
 I think. We/Webyog cannot ignore this, as we compete with Oracle (SQLyog
 - WB, MONyog - MEM).  We have to consider to implement a more intuitive
 and advisory way of displaying EXPLAIN results (for non-expert users
 primarily of course). The JSON format is interesting for us in the context.

 -- Peter





 On Fri, Sep 28, 2012 at 4:50 PM, Vladislav Vaintroub 
 w...@montyprogram.com wrote:



  -Original Message-
  From: maria-discuss-
  bounces+wlad=montyprogram@lists.launchpad.net [mailto:maria-
  discuss-bounces+wlad=montyprogram@lists.launchpad.net] On Behalf
  Of Michael Widenius
  Sent: Freitag, 28. September 2012 16:04
  To: Peter Laursen; i...@askmonty.org; tim...@askmonty.org;
  pser...@askmonty.org
  Cc: Maria Discuss; Maria Developers
  Subject: Re: [Maria-discuss] [Maria-developers] Json Explain
 
 
  For the moment we don't have a plan for that.
 
  The main reason is that the MariadB optimizer people don't like the
  implementation and we are not sure how useful the current output
  really is.
 

 I guess json  is not for normal people to read , it is for programs to
 analyze and ,for example, display in a visually pleasing fashion. I
 believe
 this is the reason why Peter asks, and (I guess) the reason why Workbench
 has visual explain feature now for 5.6+.
 http://www.arubin.org/blog/2012/09/26/mysql-visual-explain/



___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] [Maria-discuss] Json Explain

[Peter Laursen]

BTW: I reported this bug to MySQL:
http://bugs.mysql.com/bug.php?id=67022

-- Peter

On Fri, Sep 28, 2012 at 5:18 PM, Peter Laursen peter_laur...@webyog.comwrote:

 @wlad is completely right!

 Workbench introduced a Visual Explain based on JSON EXPLAIN as Blogged
 here: http://www.arubin.org/blog/2012/09/26/mysql-visual-explain/

 The very reason why JSON EXPLAIN was introduced in MySQL 5.6 could be that
 Oracle develops the server and tools (WB, Enterprirse Monitor primarily) in
 parallel.  Some recently introduced features in the server could be
 introduced for the primary reason that they should be 'exploited' by MEM
 and/or WB.  JSON EXPLAIN is one. Another example is the Performance_Schema
 table introduced in 5.6.6 (I don't remember the table name)  that records
 an 'aggregated summary' of queries' performance. Actually this table has
 about the same information as what MONyog 'Query Analyzer' module displays
 in its most simple display mode (but MONyog can be 'drilled down' to a more
 detailed view).

 So Oracle *thinks* the server and their most important tools *as a whole*,
 I think. We/Webyog cannot ignore this, as we compete with Oracle (SQLyog
 - WB, MONyog - MEM).  We have to consider to implement a more intuitive
 and advisory way of displaying EXPLAIN results (for non-expert users
 primarily of course). The JSON format is interesting for us in the context.

 -- Peter





 On Fri, Sep 28, 2012 at 4:50 PM, Vladislav Vaintroub 
 w...@montyprogram.com wrote:



  -Original Message-
  From: maria-discuss-
  bounces+wlad=montyprogram@lists.launchpad.net [mailto:maria-
  discuss-bounces+wlad=montyprogram@lists.launchpad.net] On Behalf
  Of Michael Widenius
  Sent: Freitag, 28. September 2012 16:04
  To: Peter Laursen; i...@askmonty.org; tim...@askmonty.org;
  pser...@askmonty.org
  Cc: Maria Discuss; Maria Developers
  Subject: Re: [Maria-discuss] [Maria-developers] Json Explain
 
 
  For the moment we don't have a plan for that.
 
  The main reason is that the MariadB optimizer people don't like the
  implementation and we are not sure how useful the current output
  really is.
 

 I guess json  is not for normal people to read , it is for programs to
 analyze and ,for example, display in a visually pleasing fashion. I
 believe
 this is the reason why Peter asks, and (I guess) the reason why Workbench
 has visual explain feature now for 5.6+.
 http://www.arubin.org/blog/2012/09/26/mysql-visual-explain/



___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] [Maria-discuss] Json Explain

[Peter Laursen]

+ http://bugs.mysql.com/bug.php?id=67023 -- Peter

On Sun, Sep 30, 2012 at 1:39 PM, Peter Laursen peter_laur...@webyog.comwrote:

 BTW: I reported this bug to MySQL:
 http://bugs.mysql.com/bug.php?id=67022

 -- Peter

 On Fri, Sep 28, 2012 at 5:18 PM, Peter Laursen 
 peter_laur...@webyog.comwrote:

 @wlad is completely right!

 Workbench introduced a Visual Explain based on JSON EXPLAIN as Blogged
 here: http://www.arubin.org/blog/2012/09/26/mysql-visual-explain/

 The very reason why JSON EXPLAIN was introduced in MySQL 5.6 could be
 that Oracle develops the server and tools (WB, Enterprirse Monitor
 primarily) in parallel.  Some recently introduced features in the server
 could be introduced for the primary reason that they should be 'exploited'
 by MEM and/or WB.  JSON EXPLAIN is one. Another example is the
 Performance_Schema table introduced in 5.6.6 (I don't remember the table
 name)  that records an 'aggregated summary' of queries' performance.
 Actually this table has about the same information as what MONyog 'Query
 Analyzer' module displays in its most simple display mode (but MONyog can
 be 'drilled down' to a more detailed view).

 So Oracle *thinks* the server and their most important tools *as a
 whole*, I think. We/Webyog cannot ignore this, as we compete with Oracle
 (SQLyog - WB, MONyog - MEM).  We have to consider to implement a more
 intuitive and advisory way of displaying EXPLAIN results (for non-expert
 users primarily of course). The JSON format is interesting for us in the
 context.

 -- Peter





 On Fri, Sep 28, 2012 at 4:50 PM, Vladislav Vaintroub 
 w...@montyprogram.com wrote:



  -Original Message-
  From: maria-discuss-
  bounces+wlad=montyprogram@lists.launchpad.net [mailto:maria-
  discuss-bounces+wlad=montyprogram@lists.launchpad.net] On Behalf
  Of Michael Widenius
  Sent: Freitag, 28. September 2012 16:04
  To: Peter Laursen; i...@askmonty.org; tim...@askmonty.org;
  pser...@askmonty.org
  Cc: Maria Discuss; Maria Developers
  Subject: Re: [Maria-discuss] [Maria-developers] Json Explain
 
 
  For the moment we don't have a plan for that.
 
  The main reason is that the MariadB optimizer people don't like the
  implementation and we are not sure how useful the current output
  really is.
 

 I guess json  is not for normal people to read , it is for programs to
 analyze and ,for example, display in a visually pleasing fashion. I
 believe
 this is the reason why Peter asks, and (I guess) the reason why Workbench
 has visual explain feature now for 5.6+.
 http://www.arubin.org/blog/2012/09/26/mysql-visual-explain/




___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] [Maria-discuss] Json Explain

[Peter Laursen]

I don't claim we will necessarily need it! :-)

I was only asking.  No more comments at the moment.  I will update here if
I think I have a reason to!

Thanks for considering!


-- Peter

On Sun, Sep 30, 2012 at 7:13 PM, Igor Babaev i...@askmonty.org wrote:

 Peter,

 You are right that EXPLAIN in any format has nothing to do with the
 optimizer. Looking at the piece of the MySQL code that forms the strings
 for the EXPLAIN anyone could easily come up with the patch providing
 JSON format for the EXPLAIN (even with the extensions of MySQL 5.6) and
 it would take him/her 2-3 days at most (maybe even a few hours).

 That's why we are reluctant to pull the existing implementation of JSON
 format from MySQL 5.6 into MariaDB. The patch is huge and overburdened
 with unneeded complexities. Besides it contains a lot of restructuring
 code that has nothing to do with the feature itself.

 Personally I think that the content in the current EXPLAIN (including
 the content of the EXPLAIN EXTENDED) is so shallow that any graphical
 representation hardly can help it (compare it, for example, with the
 info provided by MS SQL server).

 If, nevertheless, you badly need the feature and is ready to co-sponsor
 the feature (together with MP AB) we could discuss the details of the
 possible simple implementation. And of course we will support it in
 MariaDB if anybody else provide us with a patch for such an implementation.

 Regards,
 Igor.

 On 09/30/2012 04:23 AM, Peter Laursen wrote:
  I do not see why this should be a concern for the optimizer team.
 
  The output from EXPLAIN (in any format) does not affect optimizer's
  operation but only provides information of *optimizer result*. The
  format chosen is (?) applied is *after* not *before* or *during* the
  optimization process.
 
  TRADITIONAL EXPLAIN returns the result as an **array**.  JSON EXPLAIN
  returns the result as a single (Json-formatted) **string** (not unlike
  SHOW ENGINE INNODB STATUS, btw).  But both should have exactly the same
  information - and if they don't it is a bug with JSON EXPLAIN in MySQL
  5.6 IMO.
 
  But as I am not well-versed in server internals, I could have
  ovelooked/misunderstood something, of course.
 
  -- Peter
 
  On Fri, Sep 28, 2012 at 5:18 PM, Peter Laursen peter_laur...@webyog.com
  mailto:peter_laur...@webyog.com wrote:
 
  @wlad is completely right!
 
  Workbench introduced a Visual Explain based on JSON EXPLAIN as
  Blogged here:
  http://www.arubin.org/blog/2012/09/26/mysql-visual-explain/
 
  The very reason why JSON EXPLAIN was introduced in MySQL 5.6 could
  be that Oracle develops the server and tools (WB, Enterprirse
  Monitor primarily) in parallel.  Some recently introduced features
  in the server could be introduced for the primary reason that they
  should be 'exploited' by MEM and/or WB.  JSON EXPLAIN is one.
  Another example is the Performance_Schema table introduced in 5.6.6
  (I don't remember the table name)  that records an 'aggregated
  summary' of queries' performance. Actually this table has about the
  same information as what MONyog 'Query Analyzer' module displays in
  its most simple display mode (but MONyog can be 'drilled down' to a
  more detailed view).
 
  So Oracle *thinks* the server and their most important tools *as a
  whole*, I think. We/Webyog cannot ignore this, as we compete with
  Oracle (SQLyog - WB, MONyog - MEM).  We have to consider to
  implement a more intuitive and advisory way of displaying EXPLAIN
  results (for non-expert users primarily of course). The JSON format
  is interesting for us in the context.
 
  -- Peter
 
 
 
 
 
  On Fri, Sep 28, 2012 at 4:50 PM, Vladislav Vaintroub
  w...@montyprogram.com mailto:w...@montyprogram.com wrote:
 
 
 
   -Original Message-
   From: maria-discuss-
   bounces+wlad=montyprogram@lists.launchpad.net
  mailto:montyprogram@lists.launchpad.net [mailto:maria-
  mailto:maria-
   discuss-bounces+wlad=montyprogram@lists.launchpad.net
  mailto:montyprogram@lists.launchpad.net] On Behalf
   Of Michael Widenius
   Sent: Freitag, 28. September 2012 16:04
   To: Peter Laursen; i...@askmonty.org
  mailto:i...@askmonty.org; tim...@askmonty.org
  mailto:tim...@askmonty.org;
   pser...@askmonty.org mailto:pser...@askmonty.org
   Cc: Maria Discuss; Maria Developers
   Subject: Re: [Maria-discuss] [Maria-developers] Json Explain
  
  
   For the moment we don't have a plan for that.
  
   The main reason is that the MariadB optimizer people don't
  like the
   implementation and we are not sure how useful the current
 output
   really is.
  
 
  I guess json  is not for normal people to read , it is for
  programs

[Maria-developers] Json Explain

[Peter Laursen]

Is Explain output in Json format planned in MariaDB (refer
http://glebshchepa.blogspot.in/2012/04/optimizer-new-explain-formatjson.html)
?

If so when? and will the implementation details and output format be fully
identical to Oracle/MySQL 5.6?

(I did not find it mentioned here:
http://monty-says.blogspot.dk/2012/09/now-is-good-time-to-be-part-of-future.html
http://blog.mariadb.org/mariadb-directions/

.. sorry if I overlooked it somewhere)


-- Peter
-- Webyog
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] [Maria-discuss] Json Explain

[Peter Laursen]

@wlad is completely right!

Workbench introduced a Visual Explain based on JSON EXPLAIN as Blogged
here: http://www.arubin.org/blog/2012/09/26/mysql-visual-explain/

The very reason why JSON EXPLAIN was introduced in MySQL 5.6 could be that
Oracle develops the server and tools (WB, Enterprirse Monitor primarily) in
parallel.  Some recently introduced features in the server could be
introduced for the primary reason that they should be 'exploited' by MEM
and/or WB.  JSON EXPLAIN is one. Another example is the Performance_Schema
table introduced in 5.6.6 (I don't remember the table name)  that records
an 'aggregated summary' of queries' performance. Actually this table has
about the same information as what MONyog 'Query Analyzer' module displays
in its most simple display mode (but MONyog can be 'drilled down' to a more
detailed view).

So Oracle *thinks* the server and their most important tools *as a whole*,
I think. We/Webyog cannot ignore this, as we compete with Oracle (SQLyog
- WB, MONyog - MEM).  We have to consider to implement a more intuitive
and advisory way of displaying EXPLAIN results (for non-expert users
primarily of course). The JSON format is interesting for us in the context.

-- Peter





On Fri, Sep 28, 2012 at 4:50 PM, Vladislav Vaintroub
w...@montyprogram.comwrote:



  -Original Message-
  From: maria-discuss-
  bounces+wlad=montyprogram@lists.launchpad.net [mailto:maria-
  discuss-bounces+wlad=montyprogram@lists.launchpad.net] On Behalf
  Of Michael Widenius
  Sent: Freitag, 28. September 2012 16:04
  To: Peter Laursen; i...@askmonty.org; tim...@askmonty.org;
  pser...@askmonty.org
  Cc: Maria Discuss; Maria Developers
  Subject: Re: [Maria-discuss] [Maria-developers] Json Explain
 
 
  For the moment we don't have a plan for that.
 
  The main reason is that the MariadB optimizer people don't like the
  implementation and we are not sure how useful the current output
  really is.
 

 I guess json  is not for normal people to read , it is for programs to
 analyze and ,for example, display in a visually pleasing fashion. I believe
 this is the reason why Peter asks, and (I guess) the reason why Workbench
 has visual explain feature now for 5.6+.
 http://www.arubin.org/blog/2012/09/26/mysql-visual-explain/


___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Support of the extended syntax for ANALYZE

[Peter Laursen]

 We usually don't use key words in plural.  So what about SHOW COLUMNS?
-- Peter

On Sat, May 19, 2012 at 7:41 PM, Igor Babaev i...@askmonty.org wrote:

 On 05/19/2012 04:22 AM, Sergei Golubchik wrote:
  Hi, Igor!
 
  On May 10, Igor Babaev wrote:
  Serg,
 
  Here's the patch we talked about on IRC today.
  ...
  +ANALYZE TABLE t1(COLUMN(), INDEX());
  +ANALYZE TABLE t1(COLUMN(c,e,b), INDEX(idx2,idx4));
  +ANALYZE TABLE t1(COLUMN(*), INDEX(*));
 
  I see what you want to do.
 
  I think it'll be more SQL-like, if it'll be more verbose, for example
 
ANALYZE TABLE t1 FOR COLUMNS (c,e,d) INDEXES (idx2, idx4);
 
  I would prefer to drop parentheses too, but then the grammar will become
  ambiguous :(
  And instead of double (*) it could simply be
 
ANALYZE TABLE t1 FULL;
  or ALL;
 
  it'd be similar to
 
CHECK TABLE t1 EXTENDED;
REPAIR TABLE t1 QUICK;
etc
 
  Alternatively, it could have an explicit PERSISTENT keyword:
 
ANALYZE TABLE t1 PERSISTENT; -- meaning all columns and indexes
ANALYZE TABLE t1 PERSISTENT FOR COLUMNS (c,e,d) INDEXES (idx2, idx4);

 We usually don't use key words in plural. So maybe you meant:
 ANALYZE TABLE t1 PERSISTENT FOR COLUMN (c,e,d) INDEX (idx2, idx4);
 ?

 Regards,
 Igor.

 
  That's probably the best one. Reasonably SQL-like. And the most common
  use case (analyze all) is short, it's clearly the main, default
  behavior. And the clause to specify columns and indexes extends the
  default syntax.
 
  Regards,
  Sergei
 


 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] MariaDB 5.5.21

[Peter Laursen]

Wasn't too much copy-paste done?

http://kb.askmonty.org/en/mariadb-5520-release-notes reads This is the
first 5.5-based release ..
Also http://kb.askmonty.org/en/mariadb-5521-release-notes reads  This is
the first 5.5-based release ..

I do not understand how 5.5.21 can be the first if 5.5.20 also is (but
there are lots of things in this World I do not claim to understand).  As
far as I can see it is the *second* 5.5-based MariaDB release.

-- Peter
-- Webyog

On Thu, Mar 15, 2012 at 20:30, Daniel Bartholomew db...@montyprogram.comwrote:

 All,

 I've uploaded the MariaDB 5.5.21-beta packages to the primary mirror
 and within a few hours the files will be distributed to all of the
 mirrors.

 Over the past couple of weeks I've added several items to the release
 notes page for 5.5.21 and today I created the changelog page. The pages
 are here:

 http://kb.askmonty.org/en/mariadb-5521-release-notes
 http://kb.askmonty.org/en/mariadb-5521-changelog

 Once the files are distributed I will update the pages and add
 in the download links and remove the unreleased banners from the
 pages linked to from the release notes page. I will also send out an
 announcement email, and post announcements to twitter, FB, G+, and so
 on as usual.

 Please let me know ASAP if there is anything which is not on the
 release notes page which should be (or jump in and add it).

 Thanks.

 --
 Daniel Bartholomew
 MariaDB - http://mariadb.org
 Monty Program - http://montyprogram.com
 AskMonty Knowledgebase - http://kb.askmonty.org


 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] 5.3.5 GA release : binaries are ready and tagged

[Peter Laursen]

Typo:

Note that: when Multi Ragne Read

Note that: when Multi Range Read

-- Peter

On Wed, Feb 29, 2012 at 11:04, Sergei Petrunia pser...@askmonty.org wrote:

 On Wed, Feb 29, 2012 at 12:59:55PM +0400, Sergei Petrunia wrote:
 
  (I will also look through the changes to see what should be highlighted
 in the
  changelog).

 Done, the only change is introduction of MRR and ICP counters:

 http://kb.askmonty.org/en/index-condition-pushdown#status-variables
 http://kb.askmonty.org/en/multi-range-read-optimization#status-variables

 Other than that, it's all merges from previous versions and bugfixes.

 BR
  Sergei
 --
 Sergei Petrunia, Software Developer
 Monty Program AB, http://askmonty.org
 Blog: http://s.petrunia.net/blog

 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Documentation for MWL#192: non-blocking client API

[Peter Laursen]

With what license(s) is this new libmyslclient code being released? GPL (as
in MySQL 4.0+) or 'more permissive' of some kind - BSD/Apache/whatever
(like MySQL 3.23)?

-- Peter
-- Webyog


On Tue, Feb 28, 2012 at 13:37, Kristian Nielsen kniel...@knielsen-hq.orgwrote:

 Hi Daniel!

 I have pushed MWL#192. It will be included in upcoming MariaDB 5.5.21.

 So we need documentation of the feature :-)

 I have written a first draft of this. I included it in the high-level
 description in the WL:

http://askmonty.org/worklog/Client-Sprint/?tid=192#hld

 There are two things I would ask of you:

 1. Can you take the text and prepare it properly for the Knowledgebase?
 Find
 an appropriate place, split it up as/if needed, handle markup/formatting?
 And
 feel free to correct my text in any way you see fit.

 2. The last part, Non-blocking API reference, is basically a long list of
 all the new functions and their parameters. In the draft, I just listed
 them,
 along with specific comments to a few of them as relate to the new
 feature. For the majority of them, they are just direct translation of the
 corresponding functions from the old client library, which is documented in
 the MySQL manual.

 Can you help with a suggestion on how to present this in a nice way? Maybe
 you
 want to format them each individually in some nice way, maybe link to the
 MySQL manual? Any suggestion and/or help is appreciated.

 Can you take over from here? Of course, just let me know if there is
 anything
 lacking that you need me to do, or any questions or so on.

 (The task is not urgent as such - the feature will be available from the
 next
 MariaDB 5.5 release, which is as yet unscheduled - maybe in 2-3 weeks?)

  - Kristian.

 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Feature request: Add support for a syntax check for SQL scripts

[Peter Laursen]

It is similar to a request we had from our users from time to time. An
option to *parse* SQL statement(s) *server side* without actually executing.
(EXPLAIN and EXPLAIN EXTENDED are non-complete solutions).

I think it is difficult. MySQL was never designed for it. Basically I think
that all SQL would need to go into a 'virtual blackhole' and errors and
warnings should be returned like if physical storage was used.

Some clients will do some degree of *client side* parsing (or at least
validation).  Most notably Workbench. Obviously Oracle has no license issues
with porting the YACC/bison parser code in the MySQLserver to a client of
their own. But there are also issues with WB and subtle differences of how
SQL is handled between different server versions.  A client side solution
will always suffer from this I think.  The solution is ideally *server side*
IMHO.

A solution that allows filtering SQL through the parser, executing in a
'blackhole environment' and returns errors and warnings like doing in a
'non-blackhole environvent' would do would be extremely nice. But I also
think it is extremely difficult and will require a completely revamped
architecture of the server (what may also break compability with vanilla
MySQL).


Peter
(Webyog)



On Thu, Oct 13, 2011 at 23:20, Raphael Vullriede lists.raph...@vullriede.de
 wrote:

 Hi,

 we have a lot of developers writing a lot of SQL scripts against a lot
 of different databases. These scripts usually consists of mixed DDL
 (e.g. change a column definition) and DML (e.g. adding new master data).
 Since our applications are constantly under development we'd like to add
 these scripts to our continuous integration environment.
 For that it would be great to have a feature that checks the script
 against a given database without actually executing it. It should not
 only check the SQL syntax but also if all mentioned tables, columns etc.
 exists in the given database.
 It is not possible to use transactions for that since DDL is (currently)
 not transactional.

 I'm thinking of something like this:

 SET DISABLE_EXECUTION=TRUE;

 -- here come the sql statements

 SET DISABLE_EXECUTION=FALSE;

 I've tried to write such a check with an external tool but as it turned
 out this is virtually impossible and has a lot of loopholes.

 Do you think it would be possible to implement something like this in
 the server?

 Thanks,
 Raphael



 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Feature request: Add support for a syntax check for SQL scripts

[Peter Laursen]

On Fri, Oct 14, 2011 at 00:25, m...@rpzdesign.com m...@rpzdesign.com wrote:

  Raphael:

 You are looking at validating your scripts for your nightly build.
 (continous integration)

 I believe you can get the QA from executing the scripts on a test database
 instead of working on your live data.



Not quite IMHO  Because an erroneous script may destroy the usability of the
test database. Then it will have to be reloaded what could take hours (if a
copy of the live database)  . But a 'virtualization of SQL effect' would
require huge memory and/or huge numbers of temporary tables (that also may
take hours to rebuild!). + lots of changes in the server.

The current and practical solution is using a staging server, transactions
(with or without savepoints), synchronization systems, file system snapshots
(for fast return to last non-error situation) etc. etc. But a *visionary
approach* should be welcomed!

And even with a 'virtualization of SQL effect'' a staging server should
still be used.


 If you have a lot of stored procedures or scripts, just point them to a
 test database for continous integration
 and then when you want feel ready for the nightly release, point them
 towards the production DB.

 If you need to, copy your production data over to your test DB so that you
 can run the test script.

 I actually dump all my system DDL/DML into a text file and then refactor
 the SQL using text find/replace and then re-load the SQL back into the
 server.  Then I run my test scripts against a test database before sending
 to the beta server so that users can look at the result before release.
 This happens almost every night.

 That helpful?

 Marco
 dentro de perez zeledon


 On 10/13/2011 6:11 PM, Peter Laursen wrote:

 It is similar to a request we had from our users from time to time. An
 option to *parse* SQL statement(s) *server side* without actually executing.
 (EXPLAIN and EXPLAIN EXTENDED are non-complete solutions).

  I think it is difficult. MySQL was never designed for it. Basically I
 think that all SQL would need to go into a 'virtual blackhole' and errors
 and warnings should be returned like if physical storage was used.

  Some clients will do some degree of *client side* parsing (or at least
 validation).  Most notably Workbench. Obviously Oracle has no license issues
 with porting the YACC/bison parser code in the MySQLserver to a client of
 their own. But there are also issues with WB and subtle differences of how
 SQL is handled between different server versions.  A client side solution
 will always suffer from this I think.  The solution is ideally *server side*
 IMHO.

  A solution that allows filtering SQL through the parser, executing in a
 'blackhole environment' and returns errors and warnings like doing in a
 'non-blackhole environvent' would do would be extremely nice. But I also
 think it is extremely difficult and will require a completely revamped
 architecture of the server (what may also break compability with vanilla
 MySQL).


  Peter
 (Webyog)



 On Thu, Oct 13, 2011 at 23:20, Raphael Vullriede 
 lists.raph...@vullriede.de wrote:

 Hi,

 we have a lot of developers writing a lot of SQL scripts against a lot
 of different databases. These scripts usually consists of mixed DDL
 (e.g. change a column definition) and DML (e.g. adding new master data).
 Since our applications are constantly under development we'd like to add
 these scripts to our continuous integration environment.
 For that it would be great to have a feature that checks the script
 against a given database without actually executing it. It should not
 only check the SQL syntax but also if all mentioned tables, columns etc.
 exists in the given database.
 It is not possible to use transactions for that since DDL is (currently)
 not transactional.

 I'm thinking of something like this:

 SET DISABLE_EXECUTION=TRUE;

 -- here come the sql statements

 SET DISABLE_EXECUTION=FALSE;

 I've tried to write such a check with an external tool but as it turned
 out this is virtually impossible and has a lot of loopholes.

 Do you think it would be possible to implement something like this in
 the server?

 Thanks,
 Raphael



 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp


 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp


 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] 5.5 merge status

[Peter Laursen]

A maybe provocatice question: Did you consider to discard MySQL 5.5 and
focus on 5.6 instead for the next major MariaDB relelase?

-- PETER

On Fri, Oct 7, 2011 at 22:45, Sergei Golubchik s...@askmonty.org wrote:

 Hi, Kristian!

 About LOCK_log, LOCK_index, LOCK_thread_count and the Bug#62614:

 1. In mysql-5.5.13, that we're merging with, LOCK_thread_count is called
   *after* LOCK_log and LOCK_index. Perhaps it was your merge of log.cc
   where you swapped them.

 2. But in the latest 5.5 as on launchpad, LOCK_thread_count comes before
   LOCK_log and LOCK_index - they've changed it recently.

 3. LOCK_thd_data should go after LOCK_thread_count, because
   LOCK_thread_count is taken around 'delete thd', and LOCK_thd_data -
   in the THD destructor.

 4. LOCK_log should go after LOCK_thd_data, because LOCK_thd_data is
   taken around THD::awake(), and THD::awake() locks,
   mysys_var-current_mutex, which is LOCK_log in
   MYSQL_BIN_LOG::wait_for_update_relay_log()

 5. from 3 and 4 follows that LOCK_thread_count should be locked before
   LOCK_log, not after. Incidentally, when I did that, almost all safemutex
   deadlock detector warnings dissapeared (those that I've seen in every
   rpl test; there are be few in individual tests still).

 Regards,
 Sergei

 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

[Maria-developers] Microseconds support in MariaDB 5.3.

[Peter Laursen]

I noticed: http://askmonty.org/blog/the-2-year-old-mariadb/ The support for
microseconds in TIMESTAMP, DATETIME, and TIME.

I fully agree the 'full seconds support only' has been a sever limitation in
MySQL. But I have two concerns with ths:

1)
'noisyness'. On not very fast systems the last digits of a TIME in
microseconds should not be considered too much important.  It depends on
what else the system is doing at the time. I think for lots of users
milliseconds and not microseconds would be better/more relevant.  It is not
always a lot of digits can be proven true.  When we went to school we were
all taught not to present results in natural sciences more accurate than the
accuracy of data sources and measurements. Providing too many digits in a
resuslt actually caused a lower score in my highschool!

2)
Compability.  There is a problem with UPDATES. A client/application written
for MySQL may assume 'full seconds support only' and may generate the
current MySQL format byte format in the WHERE clause (typically if the
client reserves a 14 byte buffer for TIMERSTAMPS etc).  In SQL:

UPDATE table SET column = 'something' WHERE  time_column = '01:01:01':
.. this update will fail if the currently stored value is
'01:01:01:010001'; and the rigth query in the context would be.
UPDATE table SET column = 'something' WHERE  time_column =
'01:01:01:010001';


Ideally I think there should be a configuration parameter and a global
variable to SET time_accuracy = full_second|millisecond|microsecond.


Did somebody have considerations about same? I definitely think that lots of
applications using a TIME|TIMESTAMP|DATETIME column in the WHERE-clause of
an UPDATE statement will need some rewrite to be upgradable to MariaDB 5.3


-- Peter
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] [Maria-discuss] Microseconds support inMariaDB 5.3.

[Peter Laursen]

@Philip .. I have one more question.  Can libmysql as distributed by Oracle
handle those extended precision DATE(TIME)STAMPs - or will only the one
distributed with MariaDB do properly??

-- Peter

On Wed, Sep 21, 2011 at 16:51, Philip Stoev phi...@stoev.org wrote:

 That is fine then!  Only a little confusing thing is that as far as I know
 TIMESTAMP(14) is supported in MySQL 5.1 (and abandoned in MySQL 5.5) - so
 probably still in MariaDB as well.  So maybe N should rather have been 17
 or
 20 (the byte length)?


 TIMESTAMP(14) has been removed in MariaDB as well.



___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] WL#202 New (by Monty): Extend progress reporting

[Peter Laursen]

I understand that this is implemented in the command line client, but what
about the C-API (and what other connectors you may distribute)?

Peter
Webyog


On Thu, Jun 30, 2011 at 13:04, worklog-nore...@askmonty.org wrote:

 ---
  WORKLOG TASK
 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 TASK...: Extend progress reporting
 CREATION DATE..: Thu, 30 Jun 2011, 11:04
 SUPERVISOR.: Monty
 IMPLEMENTOR:
 COPIES TO..:
 CATEGORY...: Server-RawIdeaBin
 TASK ID: 202 (http://askmonty.org/worklog/?tid=202)
 VERSION: Server-5.3
 STATUS.: Un-Assigned
 PRIORITY...: 60
 WORKED HOURS...: 0
 ESTIMATE...: 80 (hours remain)
 ORIG. ESTIMATE.: 80

 PROGRESS NOTES:



 DESCRIPTION:

 MariaDB 5.3 supports progress reporting for ALTER TABLE and some other
 comands.
 See http://kb.askmonty.org/en/progress-reporting

 The task is to expand this to other commands and storage engines.


 ESTIMATED WORK TIME

 ESTIMATED COMPLETION DATE
 ---
 WorkLog (v4.0.0)




 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] WL#202: Extend progress reporting

[Peter Laursen]

I did already.  And it reads

*Clients that supports progress reporting:
* The mysql command line client, starting from version 15.0 (comes with
MariaDB 5.3).
* mytop which comes with MariaDB 5.3 has a '%' column that shows the
progress.*
*
*
It does not list the C-API.  maybe you should add Clients compiled with the
C-API as shipped with MariaDB 5.3+ provided that ... . It it not all that
the command line supports that is suppored in API (examples: \G-delimiter
and SOURCE statement for instance) so listing CLI does not necessary. *
*
*
*
Now I have read 'deeper' and it looks like C-API is working too.  But I
think it should be listed explicitly if supported.*
*

-- Peter

On Thu, Jun 30, 2011 at 13:29, Sergei Golubchik s...@askmonty.org wrote:

 Hi, Peter!

 On Jun 30, Peter Laursen wrote:
  I understand that this is implemented in the command line client, but
 what
  about the C-API (and what other connectors you may distribute)?

 See http://kb.askmonty.org/en/progress-reporting

 Regards,
 Sergei

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] WL#202: Extend progress reporting

[Peter Laursen]

The question is whether you can compile your own client(s) with this option.
In other words 'add to the list'.  I am not a coder so I do not understand
the full details of the document.  I just do not find a clear statement in
plain words (not code) that a client may be built with this option in
addition to the 2 that ship with MariaDB 5.3 and what the requirements are.

BTW: *Webyog* is NOT a *client*.  It is a *company.  Clients *are *SQLyog*
and *MONyog* (and the latter is actually also a *server* at the same time!
:-)


Peter


On Thu, Jun 30, 2011 at 15:46, Sergei Golubchik s...@askmonty.org wrote:

 Hi, Peter!

 On Jun 30, Peter Laursen wrote:
  I did already.  And it reads
 
Clients that supports progress reporting:
* The mysql command line client, starting from version 15.0 (comes
  with MariaDB 5.3).
* mytop which comes with MariaDB 5.3 has a '%' column that shows the
  progress.
 
  It does not list the C-API.  maybe you should add Clients compiled with
 the
  C-API as shipped with MariaDB 5.3+ provided that ... . It it not all
 that
  the command line supports that is suppored in API (examples: \G-delimiter
  and SOURCE statement for instance) so listing CLI does not necessary.

 I'm not sure I understand.
 To show progress report information, a *client* needs to support it -
 not just the *API*. From all the clients, only mysql command line client
 and mytop support this at the moment. And the page says it.

 C-API itself is not a client, as far as I can see it, it's an API.
 For example, Webyog is a client.

  On Thu, Jun 30, 2011 at 13:29, Sergei Golubchik s...@askmonty.org
 wrote:
 
   On Jun 30, Peter Laursen wrote:
I understand that this is implemented in the command line client,
but what about the C-API (and what other connectors you may
distribute)?

 I think I misunderstood your question. I'm sorry.

 You mean whether C-API supports progress reporting - and the answer is
 yes, absolutely.

 But originally I thought you were asking what is the C-API or this
 feature, how one can add progress reporting support to his MySQL
 client. And the answer was

   See http://kb.askmonty.org/en/progress-reporting

 because, indeed, the API is described there, in the Knowledge Base.

 Regards,
 Sergei


___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] WL#202: Extend progress reporting

[Peter Laursen]

Let me add that the reason I am asking is that for us (MONyog in particular)
it would be interesting to support it. To do so will we need to replace the
client library/C-API to the one shipped with MariaDB 5.3?

-- Peter

On Thu, Jun 30, 2011 at 16:02, Peter Laursen peter_laur...@webyog.comwrote:

 The question is whether you can compile your own client(s) with this
 option. In other words 'add to the list'.  I am not a coder so I do not
 understand the full details of the document.  I just do not find a clear
 statement in plain words (not code) that a client may be built with this
 option in addition to the 2 that ship with MariaDB 5.3 and what the
 requirements are.

 BTW: *Webyog* is NOT a *client*.  It is a *company.  Clients *are *SQLyog*
 and *MONyog* (and the latter is actually also a *server* at the same time!
 :-)


 Peter


 On Thu, Jun 30, 2011 at 15:46, Sergei Golubchik s...@askmonty.org wrote:

 Hi, Peter!

 On Jun 30, Peter Laursen wrote:
  I did already.  And it reads
 
Clients that supports progress reporting:
* The mysql command line client, starting from version 15.0 (comes
  with MariaDB 5.3).
* mytop which comes with MariaDB 5.3 has a '%' column that shows the
  progress.
 
  It does not list the C-API.  maybe you should add Clients compiled with
 the
  C-API as shipped with MariaDB 5.3+ provided that ... . It it not all
 that
  the command line supports that is suppored in API (examples:
 \G-delimiter
  and SOURCE statement for instance) so listing CLI does not necessary.

 I'm not sure I understand.
 To show progress report information, a *client* needs to support it -
 not just the *API*. From all the clients, only mysql command line client
 and mytop support this at the moment. And the page says it.

 C-API itself is not a client, as far as I can see it, it's an API.
 For example, Webyog is a client.

  On Thu, Jun 30, 2011 at 13:29, Sergei Golubchik s...@askmonty.org
 wrote:
 
   On Jun 30, Peter Laursen wrote:
I understand that this is implemented in the command line client,
but what about the C-API (and what other connectors you may
distribute)?

 I think I misunderstood your question. I'm sorry.

 You mean whether C-API supports progress reporting - and the answer is
 yes, absolutely.

 But originally I thought you were asking what is the C-API or this
 feature, how one can add progress reporting support to his MySQL
 client. And the answer was

   See http://kb.askmonty.org/en/progress-reporting

 because, indeed, the API is described there, in the Knowledge Base.

 Regards,
 Sergei



___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] MariaDB limits

[Peter Laursen]

@Sergei .. I cannot reply on behalf of Marian, of course.  But the current
'limitation_per_hour' user settings would have same considerations in this
respect as  'limitation_per_24hour' proposed by Marian would as far as I can
see.

Either it is
* between current_time and current_day:00:00:00  -- from midnight if you
like
* or between current time and current_time-1day . -- from 24 hours ago

What does 'limitation_per_hour' user settings do currently?
* between now() and hour(now()) -- from last time minutes were '00'
* or (between now()-1day) and hour(now())  -- from 1 hour ago

(hope you understand my pseudocode and explanation)


For consistence I think that 'limitation_per_24hour' should work exactly
like current  'limitation_per_hour'  do. I could actually suggest a (global
only) server variable/startup option '--user_limit_time_interval' that
manages if settings in ´mysql`.'user` should be per
second|minute|hour|day|week|month ...

Or just introduce it in seconds and let 3600 be default. Then
--user_limit_time_interval=7200 would change the limitations in
´mysql`.'user` to have effect for a 2-hour period and not a 1-hour period.

Not that I need such thing myself but that would be a consistent and
compatible implementation of Marian's request if I understand.

-- Peter

On Tue, Jun 21, 2011 at 14:23, Sergei Golubchik s...@askmonty.org wrote:

 Hi, Marian!

 On Jun 20, Marian Marinov wrote:
  
   But what per-user limitations do you want to add exactly?
 
  I'm interested in the CPU_TIME, BUSY_TIME, BYTES_RECEIVED and
  BYTES_SEND.

 What do you plan to do when a user reaches his limit on, say, CPU_TIME?
 Lock the account till the end of the 24h period?

 Regards,
 Sergei

 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] MariaDB limits

[Peter Laursen]

@Marain .. you probably know this:
http://dev.mysql.com/doc/refman/5.1/en/user-resources.html . This is same
for MySQL and MariaDB.

I_S is a *read-only* database. And if you want to add more configurable
per-user limitations such should IMHO go to the `mysql` database. I also
don't think (for compability) that it should be more rows added
`mysql`.`user` then, but maybe rather a new table specific for such patch (
`mysql`.`user_addon` or whatever).

But what per-user limitations do you want to add exactly?


Peter
(from Webyog and thus not a MariaDB developer - just a follower here)


On Mon, Jun 20, 2011 at 20:03, Marian Marinov m...@yuhu.biz wrote:

 Hello guys,
 I have a lot of clients requesting some kind of per user limiting based on
 the
 information from the STATISTICS tables.

 I'm thinking of creating a patch that will add this functionality by
 creating
 two more tables in the INFORMATION_SCHEMA:
  USER_LIMITS
  CLIENT_LIMITS

 They will have some parts of the structure of USER_STATISTICS and
 CLIENT_STATISTICS and will keep only values for limits. By default a 0
 would
 mean no limit.

 Do you have any comments about my aproach?

 Would you be willing to accept a patch that adds such functionality?

 I want to know before I start work on this project if the community is
 interested in such enhancement of MariaDB.

 Regards,
 Marian

 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] [Maria-discuss] Reqeust for SHOW FULL FIELDS FROM and virtual tables in MariaDB

[Peter Laursen]

I have a few more points to consider:

CREATE TABLE table1 (as before);

SET SQL_MODE = 'strict_all_tables';

INSERT INTO `test`.`table1`(`a`,`b`,`c`,`d`) VALUES ( '1','a',NULL,NULL); --
success
SHOW WARNINGS -- empty set
-- this is actually good, even a little inconsistent with what comes next.
But GRID-type GUI clients could have difficulties working with virtual
colums if it behaved differently.

UPDATE `test`.`table1` SET `d`='b' WHERE `a`='1' AND `b`='a' AND `c`='1' AND
`d`='a';
SHOW WARNINGS; -- 1647 The value specified for computed column 'd' in table
'table1' ignored
-- In strict mode we should have an error and not a warning here, I think.

INSERT INTO `test`.`table1`(`a`,`b`,`c`,`d`) VALUES ( '2','b','3','d');
-- again two warnings (not errors) here for 3rd and 4th column's INSERT

-- In summary
-- I like that it is not returning warnings or errors for values
INSERTED/UPDATED to NULL.
-- but in strict mode I think errors whoud be returned where warnings
currently are. Virtual columns should be sql_mode-aware'.

-- Peter


On Fri, Jun 3, 2011 at 05:24, Arjen Lentz ar...@openquery.com wrote:

 Hi Peter, all

  From: Peter Laursen peter_laur...@webyog.com
 
  Refer http://kb.askmonty.org/v/virtual-columns - the example
 
  CREATE TABLE table1 (
  a INT NOT NULL,
  b VARCHAR(32),
  c INT AS (a MOD 10) virtual,
  d VARCHAR(5) AS (LEFT(b,5)) persistent);
 
  now
 
  SHOW FULL FIELDS FROM table1;
 
  Field Type Collation Null Key Default Extra Privileges Comment
  -- --- - -- -- --- ---
  --- ---
  a int(11) (NULL) NO (NULL) select,insert,update,references
  b varchar(32) latin1_swedish_ci YES (NULL)
  select,insert,update,references
  c int(11) (NULL) YES (NULL) VIRTUAL select,insert,update,references
  d varchar(5) latin1_swedish_ci YES (NULL) VIRTUAL
  select,insert,update,references
 
  I request that 'extra' column should return either PERSISTENT or 
  VIRTUAL, PERSISTENT for column `d`. The reason is that the output
  from SHOW FULL FIELDS returns an *array* (that will not need to be
  parsed) as opposite to SHOW CREATE TABLE. Accordingly SHOW FULL
  FIELDS is much easier to use for an 'unintelligent client' as
  opposed to an 'intelligent (or ignorant for that sake :-) ) human
  user to decide on special properties for a column.

 I'm for this.
 Perhaps use BASE rather than PERSISTENT, in line with views  base tables -
 since it's similar stuff.
 And of course SHOW FULL TABLES will show BASE TABLE and VIEW already.

 Cheers,
 Arjen.

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

[Maria-developers] Reqeust for SHOW FULL FIELDS FROM and virtual tables in MariaDB

[Peter Laursen]

Refer http://kb.askmonty.org/v/virtual-columns - the example

CREATE TABLE table1 (
a INT NOT NULL,
b VARCHAR(32),
c INT AS (a MOD 10) virtual,
d VARCHAR(5) AS (LEFT(b,5)) persistent);


now

SHOW FULL FIELDS FROM table1;

Field Type Collation Null Key Default Extra Privileges Comment
-- --- - -- -- --- ---
--- ---
a int(11) (NULL) NO (NULL) select,insert,update,references
b varchar(32) latin1_swedish_ci YES (NULL) select,insert,update,references
c int(11) (NULL) YES (NULL) VIRTUAL select,insert,update,references
d varchar(5) latin1_swedish_ci YES (NULL) VIRTUAL
select,insert,update,references

I request that 'extra' column should return either PERSISTENT or 
VIRTUAL, PERSISTENT for column `d`.  The reason is that the output from
SHOW FULL FIELDS returns an *array* (that will not need to be parsed)  as
opposite to SHOW CREATE TABLE. Accordingly SHOW FULL FIELDS is much easier
to use for an 'unintelligent client' as opposed to an 'intelligent (or
ignorant for that sake :-) ) human user to decide on special properties for
a column.


Peter
Webyog
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] mysql improvement idea - field type file

[Peter Laursen]

Actually I believe that could be implemented as a storage engine? The
database would be the par of the file system that mysqld can access for both
read and write. Each table in it would be a folder and every distinct value
a file. A few additional syntactical constructs would be needed (but lots of
storage engines already have such). And such tables could be restricted to
one column (an 'array of files' does not make sense here I think).

example:
CREATE TABLE webportals ENGINE FILESYSTEM AT /var/lib/mysql; -- will create
a folder named 'webportals' if not exists.
INSERT INTO webportals 'myfunnywebsiteportal.html' VALUES ('a string');--
will create file 'myfunnywebsiteportal.html' if not exists and populate it
with 'a string'. LOAD DATA could be used to populate the file too.
:-)

It has some security concerns though to access file system like that!
Indexing of data is an issue too - but such tables will probably have few
records - most often a few files only -  so maybe not really an issue. But
such engine could also have an equivalent to the .MYI file.

(Just one half cent from a non-coder.  And maybe PBXT 'Blob-streaming
engine' does something of the kind already? And the Microsoft text-ODBC
driver actually already does something similar in considering a folder in
file system a table equivalent)

Peter
(Webyog)

On Thu, May 19, 2011 at 16:51, Tõnu Samuel t...@jes.ee wrote:

 (
 1. Sent this mail few days ago to Monty but no answer yet. I know, he is
 busy man.
 2. I use name MySQL because this is real name for me. Oracle still
 sucks:P
 )


 Hi!

 We all have seen cases where people try to use SQL for something what
 does not fit there. Reason is simple - file system itself is very good
 database for some type of objects and queries.

 One common MySQL usage scenario is web portal. Often portal has some
 sort of news and photos accompanying it. My idea is to make some sort of
 clever way to store images within MySQL making their read/write as fast
 as possible and meanwhile giving extra value to user who shouldn't care
 about data integrity keeping data in and out of SQL coherent. Also would
 be cool to get all required data with single query.

 I think best way to implement this is to introduce field type file
 which is stored outside of usual data storage. Only his physical
 location on disk is stored in MyISAM or similar. This is exactly same as
 people keep file name in CHAR currently but we provide method to fetch
 file contents with same query. Also we can implement cool replication to
 keep same file on all servers consistent, way to backup things via
 mysqldump etc

 Actually idea is bit wider but what you think generally?

  Tõnu

 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

[Maria-developers] 5.2.6 .msi isntaller questions issues

[Peter Laursen]

I think this is for @wlad! :-)


I just installed 5.2.6 using the new .msi installer.  This was an upgrade
'on top' of the previous (5.2.3 or 5.2.4) .msi build distributed by wlad in
mailing list.

The installer worked fine,  The previos 5.2 instance was upgraded (ie.
executables and similar files replaced, old my.ini and datadir is still used
etc.). So far so good. The problem is with the configuration wizard.  What
is it supposed to do?  Run 'mysql_upgrade'? More than this or something
else?

Let me explain my setup.  Except for this MariaDB instance (running as
service 'maria52') I have both MySQL/Oracle 5.0, 5.1, 5.5 and 5.6 (running
as services 'MySQL50,  'MySQL51' ,  'MySQL55' ,  'MySQL56') . The config
wizard prompts me which instance should be upgraded an gives me a choice of
  'MySQL50 and  'MySQL51'  but not  'MySQL55', 'MySQL56' and 'maria52'.

1) Now if the wizard starts 'mysql_upgrade' it makes perfect sense not to
offer to upgrade 'MySQL55' and 'MySQL56'  (as MySQL51/MariaDb52 are 'lower'
than those -   it would be a 'downgrade' - not an 'upgrade' then - what
'mysql_upgrade' does not handle).   But ideally I think they should be
displayed but 'greyed out' or otherwise indicated that upgrading MySQL
5.5/5.6 -- MariaDB 5.2 is not possible.

2) More important: the instance that I *really* wanted to upgrade
('maria52') was not displayed.  I assume that the services' list is filtered
by the prefix 'mysql'.  Am I right?  In that case I suggest the filtering is
done on both (OR'ed) prefixes 'mysql' and 'maria'.


Anyway after just exiting the wizard before executing it everything seems
fine.  But the wizard GUI can still be 'polished' a little I think.


-- Peter Laursen
-- Webyog
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Windows installer MWL#55 finished.

[Peter Laursen]

@wlad

I came across an issue with the .msi from Oracle.
refer: http://bugs.mysql.com/bug.php?id=60830

In short: if somebody installs a 'n-bit' version and on top of this a
'm-bit' version various inconsistencies happen inside Windows system menus.
 I concluded that

1) either: a n-bit of a x.y version should refuse to install if a m-bit of
same x.y
version is installed
2) or: n-bit and m-bit should should identify themselves so that Windows can
handle them
in parallel. (not only 'MySQL Server 5.5 but MySQL Server 5.5 - 64 bit
etc.)

Is this something you have been considering?

-- Peter

On Tue, Mar 8, 2011 at 20:23, Vladislav Vaintroub w...@montyprogram.comwrote:





 *From:* Peter Laursen [mailto:peter_laur...@webyog.com]
 *Sent:* Mittwoch, 2. März 2011 11:30
 *To:* Vladislav Vaintroub
 *Cc:* Kazuhisa Ichikawa; maria-developers@lists.launchpad.net

 *Subject:* Re: [Maria-developers] Windows installer MWL#55 finished.



 It seems that http://downloads.askmonty.org/mariadb/ still has the old
 NSIS-based installer for 5.1.55? – Peter

 Yes, 5.1 will have the old installer until the end of 5.1’s life.  Also,
 in 5.2/5.3 the new installer is not pushed yet, because it is not yet
 reviewed.

 On Tue, Feb 8, 2011 at 00:46, Vladislav Vaintroub w...@montyprogram.com
 wrote:



___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] [Maria-discuss] MariaDB 5.6

[Peter Laursen]

I do not have the perfect solution. The 'forking' means that different
vendors will provide versions that add features. Before the forking started
you could simply strip out the x.y.z information from SELECT VERSION().

A recnet MariaDB example Now MariaDB has 'virtual columns'.  But how I tell
except for trying to create such and get an error? Just a loose idea:
implement SHOW EXTRA_FEATURES? This would then list all features in 'forks'
that the parallel MySQL/Oracle version has not. Then the client/user would
know what is possible to do and what is not without resorting to
try-and-error method.

Two more simple examples:
1) There is no 'have_events' variables.  A client or user will need to know
that EVENTS are available in 5.1+. If somebody would release a 'fork' named
5.1.x with´out EVENTS it would be a mess.
2) There is no way to tell if server supports LOAD DATA XML except that this
is known to be available in 5.5+

(and an old complaint of mine: there is no way to tell if a storage engine
supports FOREIGN KEYS.  Even SHOW ENGINES/SELECT FROM I_S.ENGINES does not
expose this for each engine installed.  The client/user will need to know
that this is available in InnoDB/ExtraDB and PBXT (and the discontinued
SolidDB). We have to hardcode in SQLyog that if - and only if -engine is
InnoDB | PBXT | SolidDB we enable GUI functionalities to handle FK's. But
there are so many enginess now that we cannot know them all. There could be
(or soon come) more with FK -support). Also in MONyog we would like add
supportt for 'fork' features (IS plugins - like the user statistics plugin -
for instance).  But if a user uses MONyog to monitor 200 servers where 80%
are official MySQL/Oracle version and the rest a mix of various forks
(MariaDB, PerconaServer, OurDelta etc.) it becomes a little complicated to
manage what to do and not to do for each server.  It was easier in the old
days where x.y.z information from SELECT VERSION() provided all information.
But now 5.2.z can be both MySQL 5.2 (that was later named 6.0) and MariaDB
5.2.  This is not a big deal as MySQL 5.2 is probably not used at all.  It
would be a bigger deal if mariaDB 5.6 is released based on MySQL 5.5
codebase and MySQL 5.6 introduces new major features that MariaDB 5.6 has
not. But I don't know what exactly is planned for MySQL 5.6 - however it is
out now (refer ftp://ftp.easynet.be/mysql/Downloads/MySQL-5.6/ and
http://dev.mysql.com/doc/refman/5.6/en/



Rohit will be at the UC.  I cannot tell if he will be able to join the
above-mentioned MariaDB event and how much.  He also is part of some SkySQL
event as a speaker/panel member. I will ask him to discuss this concern
where and with whom he thinks appropriate. I do not think we can expect
Oracle to be mcuh concerned about this problematic.  But I think the vendors
providing forks should - and I belive it would be in the interest of all
majorn vendors providing forks to agree on a uniform solution.



.. Peter

On Sat, Apr 9, 2011 at 17:10, Kristian Nielsen kniel...@knielsen-hq.orgwrote:

 Peter Laursen peter_laur...@webyog.com writes:

  I noticed this on planet.mysql: http://kb.askmonty.org/v/plans-for-56
 
  I *again* strongly want to discourage a major version number identical
 with
  a MySQL/Oracle release.  MySQL plans a 5.6 too and I believe that there
 is
  already a source-tree available on launchpad. I think I understand that
  MariaDB 5.6 is planned to use MySQL 5.5 codebase.  Am I correct?

 I don't think we would use 5.6 for MariaDB based on MySQL 5.5 (as opposed
 to
 MySQL 5.6) codebase. That would be confusing indeed.

 MariaDB 5.6 would be a version that included MySQL 5.6. If we need to
 release
 what we now call 5.6 before MySQL 5.6 is released/stable, I think we
 would
 need to come up something else...

 Similarly, the next release of MariaDB will be called 5.5 or 5.3, depending
 on
 whether we decide to include MySQL MySQL 5.5 or not.

  I have now posted this complaint 2 or 3 times (including the times I
  complained about the use of 5.2 for a mariaDB based on MySQL 5.1 code as
  there is alose a (now abandoned) MySQL 5.2 tree.  I never had a reply
 from a
  MariaDB 'decisionmaker'.  Could I at least request a reply this time?
  Please! :-)

 I also do not think current version schema is perfect. However, do you have
 a
 better suggestion?

 The good thing about MariaDB 5.1, 5.2, 5.3, 5.5, 5.6, ... is that given
 MariaDB X and MySQL Y, you can know that MariaDB X includes all of MySQL Y
 (and thus can be used as a drop-in replacement) as long as X = Y.

 Can we do something better that solves your concerns, and still preserves
 this
 nice property in some way?

  - Kristian.

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

[Maria-developers] MariaDB 5.6

[Peter Laursen]

I noticed this on planet.mysql: http://kb.askmonty.org/v/plans-for-56

I *again* strongly want to discourage a major version number identical with
a MySQL/Oracle release.  MySQL plans a 5.6 too and I believe that there is
already a source-tree available on launchpad. I think I understand that
MariaDB 5.6 is planned to use MySQL 5.5 codebase.  Am I correct?

The problem arises with *generic clients* (ie clients that are supposed to
work with not only one specific server version but a broad range of server
versions) - including all GUI clients. Such clients will execute a SELECT
VERSION() after connection to decide what features in the client should be
enabled or not (necessary as SHOW VARIABLES LIKE 'have_*** and SELECT
... FROM I_S cannot always be used due to incomplete instrumentation with
those)


I have now posted this complaint 2 or 3 times (including the times I
complained about the use of 5.2 for a mariaDB based on MySQL 5.1 code as
there is alose a (now abandoned) MySQL 5.2 tree.  I never had a reply from a
MariaDB 'decisionmaker'.  Could I at least request a reply this time?
Please! :-)

I repeat: It is really causing problems for *generic clients* if there are
too different 5.6's with different feature sets. What solution would you
suggest for a client that shall be able to connect to both MySQL5.6 and
MariaDB 5.6 without confusing the features of one server with the other?


Peter
Webyog
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Default parameter settings / Windows MSI installer

[Peter Laursen]

1) As I have already told I request a max_allowed_packet setting larger than
1M (in both [mysqld] and [mysqldump] sections).  Oracle-MySQL sets 1M in
[mysqld] and 16M in [mysqldump].  I prefer 64M in both actually.  The reason
is that BLOBs are commonly used to store images/photos and with recent
digital cameras (10-18 Mpixel) it is not even possible to store an image
from such cam in a single INSERT statement.  MySQL server will 'go away' or
'receive a packet too large'.

2) Oracle-MySQL sets
STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION if user
select 'strict mode' during configuration.  NO_AUTO_CREATE_USER just means
that GRANT will not create user - only CREATE USER + GRANT will.  This I do
not find important.  So I am OK with 'strict wlad mode'.  But I am not sure
that strict mode should be default as long as it is not in *nix.

3) I agree that if InnoDB is default engine then the 'pool size' should be
raised from default. Looks OK for a test/development server as typically
used in Windows (but still a very low setting for a production server)

-- Peter

On Tue, Apr 5, 2011 at 20:30, Vladislav Vaintroub w...@montyprogram.comwrote:

 Hello,
 After recent discussion about appropriate or not appropriate default
 setting
 on in my.cnf , I have created a prototype minimal settings for Windows
 installer.
 Here is the picture of  this attempt
 http://cid-ff0c950417b4f8a4.office.live.com/self.aspx/share/dbsettings.png

 For those who have familiar the 5.2 MSI installer already,  what I have
 added is a checkbox Standard configuration, explanation text, and input
 field for innodb bufferpool size (preset with RAM/8,  in my case it is
 8191/8=1023).
 Standard configuration is on by default,

 if it is on, then 4 parameters are added to the my.ini file
 1) default_storage_engine=innodb
 2) innodb_buffer_pool_size=[VALUE_IN_EDIT_BOX]M
 3) innodb_log_file_size= min(innodb_buffer_pool_size/4, 50)

 I made this formula almost out of thin air and using some blog reading and
 comments in the templates.  It is likely that 50M is more than the average
 user needs, however it only takes some disk space, and  If user has to
 increase from default 5MB , the procedure is awkward.  I checked, MySQL
 Config Wizard set this parameter to  54M on my box, so it is in  the same
 range.

 4) sql_mode=STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION

 If Standard configuration is off, hen input field for bufferpool size is
 disabled, and none of those 4 parameters  is added to my.ini

 Do you think it is useful in this form?  So far I tried to avoid
 calibration topics  altogether since it is a  controversial topic where
 people never have same  opinions. Also I tried to avoid it because I cannot
 write GUIs . However, this one change is small in and it does  not
 introduce
 additional dialogs. It makes some important  defaults the same as standard
 configuration in existing MySQL installers. I think it was PeterL who
 already asked for non-default buffer pool size already, also Monty also
 spoke about it in Lisbon.

 Comments welcome,  also those on the picture above - I'm not sure  if
 wording and use of brackets and quotes is correct.

 Wlad


___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Default parameter settings / Windows MSI installer

[Peter Laursen]

XtraDB identifies itself as 'InnoDB' (in I_S tables and SHOW ENGINES). And X
is in every respect backwards compatible with I. Even in CREATE TABLE
statments you name it 'InnoDB'. For those users not familiar with the
'political situation' around MySQL 'InnoDB' would be familiar and 'XtraDB'
unknown for many.  It could be written like 'InnoBD (XtraDB)' though.

-- Peter

On Tue, Apr 5, 2011 at 20:47, Adam M. Dutko dutko.a...@gmail.com wrote:

 I don't know if the following comments are useful but here goes...

  Here is the picture of  this attempt

 Looks nice.

  For those who have familiar the 5.2 MSI installer already,  what I have
  added is a checkbox Standard configuration, explanation text, and

 For those that aren't familiar or are new to the installer I'm
 thinking a small question mark surrounded by a circle next to the
 'Standard Configuration' textbox that when hovered over popups a more
 detailed description of what standard means for MariaDB. This would
 be in lieu of the text below the checkbox. This might make sense to
 have for the other fields too. Just a thought.

  1) default_storage_engine=innodb

 I think the storage engine that replaced innodb is now technically
 xtradb but I believe the configuration option alias innodb still
 works for compatibility. Would it make sense to point this out?

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Windows installer MWL#55 finished.

[Peter Laursen]

It seems that http://downloads.askmonty.org/mariadb/ still has the old
NSIS-based installer for 5.1.55? -- Peter

On Tue, Feb 8, 2011 at 00:46, Vladislav Vaintroub w...@montyprogram.comwrote:



  -Original Message-
  From: kah...@gmail.com [mailto:kah...@gmail.com] On Behalf Of Kazuhisa
  Ichikawa
  Sent: Sonntag, 6. Februar 2011 09:32
  To: Vladislav Vaintroub
  Cc: Philip Stoev; maria-developers@lists.launchpad.net
  Subject: Re: [Maria-developers] Windows installer MWL#55 finished.

 Hello, Kazuhisa
  No :-). My experience with MySQL installers is limited to fresh
  install. This is the first time I tried 'upgrade' and my expectation
  was purely imaginary.

 Right, there is no upgrade functionality in MySQLs installers up-to-now
 (nor
 I heard or any planning for it recently). But I noticed that both you and
 Philip had quite similar requests for the changed UI in case of  upgrade
 possible. Both of you recommended changes at the Database Properties
 dialog, I think it is wrong place, by the time you enter this dialog it is
 too late,  you should not have entered this dialog, as the intention was
 not
 create new, but upgrade existing anyway..

 So since both of my users have pointed to usability issues,  I added a new
 dialog  that comes after license agreement that and tells user  that
 upgradable instances were found and please make a choice between
  installing
 a new instance and not installing a new instance(optional upgrade one or
 more existing ones). This sounds almost like your first suggestion, but in
 own dialog. This dialog comes right before feature selection, and only
 thing
 it might do is to unselect Database Instance feature in the following
 dialog . Technically, it duplicates functionality of the feature selection
 tree. So what... I hope it adds some clarity for the user - at least tells
 the user that his existing instances *can* be upgraded. Or maybe it won't
 help that much, since user never looks at the UI anyway :) (nice article
 about that is here
 http://www.codinghorror.com/blog/2009/10/treating-user-myopia.html )

 Anyway, I uploaded the newest msis to the usual place, if somebody wants to
 play with it.

 Thanks,
 Vladislav.






 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Windows installer MWL#55 finished.

[Peter Laursen]

@Vlad

SHOW ENGINES

ENGINE Support
-
..
PBXT   NO


I think that the .zip package had PBXT enabled as default.  Can I enable it
somehow with this build? PBXT is actually *THE REASON* why MariaDB is
interesting for me.


-- Peter




On Fri, Feb 4, 2011 at 16:51, Vladislav Vaintroub w...@montyprogram.comwrote:



  -Original Message-
  From: kah...@gmail.com [mailto:kah...@gmail.com] On Behalf Of Kazuhisa
 Ichikawa
  Sent: Freitag, 4. Februar 2011 03:17
  To: Vladislav Vaintroub
  Cc: maria-developers@lists.launchpad.net
  Subject: Re: [Maria-developers] Windows installer MWL#55 finished.
 
  Hello Vladislav,

 Hello Kazuhisa,

  First of all, thanks for all the information on MSI v.s. NSIS issues.
 
   On a bright side, this is a valid bug that was simple to fix forcing
 per-machine install, so installer does not need to guess.  I
   did that and  refreshed the MSI on the download page.
 
  I confirmed the fix with the same machine/user with which I had the
  original problem. Thanks.
 
  However, I'm afraid I hit a new one. If I have MariaDB 5.1.53
  installed (by the 5.1 installer) on the same machine, the new
  installer doesn't allow me to install 5.2.5 saying:

  Previous version of MariaDB was found, that used incompatible
  installer. Please remove MariaDB 5.1.53 before you proceed with this
  installation.

 Ok, valid bug. Thanks for reporting.

 There will *still* be this message if you're trying to install 5.2.5 msi
 with existing 5.2.(5) NSIS .   For me personally  ,main reason NOT  to
 offer 5.2.4=5.2.5 autoupgrade is the fact that MariaDBs NSIS was not
 designed to run in silent mode, its popups Directory not deleted during
 upgrade  would only alienate users .

  I think this is not an intended behavior, because this kills the big
  benefit (of your new installer) of automatically upgrading older
  MariaDB instance.

 The upgrade is not always automatic,  sometimes it is semiautomatic
 (supported by the  UI tool launched at the end of installation).  Did you
 look in the WL on how upgrades are handled? Here is link just in case
 http://askmonty.org/worklog/Server-Sprint/?tid=55 .  Feedback on it  is
 welcome.


 I have fixed 5.2.5 over 5.1 NSIS installation ,the update is on usual
 place.
 http://cid-ff0c950417b4f8a4.office.live.com/browse.aspx/share


 Thanks for your efforts,
 Vladislav



 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Windows installer MWL#55 finished.

[Peter Laursen]

Thanks .. worked fine. No crash till now ... -- Peter

On Fri, Feb 4, 2011 at 17:13, Vladislav Vaintroub w...@montyprogram.comwrote:



 From: Peter Laursen [mailto:peter_laur...@webyog.com]
 Sent: Freitag, 4. Februar 2011 16:58
 To: Vladislav Vaintroub
 Cc: Kazuhisa Ichikawa; maria-developers@lists.launchpad.net
 Subject: Re: [Maria-developers] Windows installer MWL#55 finished.

 @Vlad

 SHOW ENGINES

 ENGINE Support
 -
 ..
 PBXT   NO
 I think that the .zip package had PBXT enabled as default.  Can I enable
 it somehow with this build? PBXT is actually *THE REASON* why MariaDB is
 interesting for me.


 Hi Peter,
 This Colibri unfortunately does not fly well on x64. I tried it (admittedly
 the debug version), installer crashed. I hesitate to enable it until
 https://bugs.launchpad.net/maria/+bug/688404 is fixed, or at least
 understood or handled somehow by PBXT developers.

 If you like to enable it, you can uncomment  loose-skip-pbxt in my.ini.

 Thanks!




___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Windows installer MWL#55 finished.

[Peter Laursen]

I am a little bit busy now, but will confirm tonight. -- Peter

On Wed, Feb 2, 2011 at 14:12, Vladislav Vaintroub w...@montyprogram.comwrote:



 From: Peter Laursen [mailto:peter_laur...@webyog.com]
 Sent: Dienstag, 1. Februar 2011 20:31
 To: Vladislav Vaintroub
 Cc: maria-developers@lists.launchpad.net
 Subject: Re: [Maria-developers] Windows installer MWL#55 finished.

 It is a Danish Windows (Home Premium 64 bit).

 Hi Peter,
 As it turns out,  installer had the same localization problem registering
 service on German Windows.  Fixed  now,  I uploaded the msis to the same
 place http://cid-ff0c950417b4f8a4.office.live.com/browse.aspx/share

 Thanks,
 Wlad




___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Windows installer MWL#55 finished.

[Peter Laursen]

On Wed, Feb 2, 2011 at 19:04, Vladislav Vaintroub w...@montyprogram.comwrote:



 From: Peter Laursen [mailto:peter_laur...@webyog.com]
 Sent: Mittwoch, 2. Februar 2011 17:14
 To: Vladislav Vaintroub
 Cc: maria-developers@lists.launchpad.net
 Subject: Re: [Maria-developers] Windows installer MWL#55 finished.


 Hi Peter,

 Your default install path is \program files [(x86)]. You copy the /datadir
 as a subfolder of /basedirr.
 This will cause problems on Vista+ with  UAC enabled if the server is ever
 started from commandline as a non-service (also if the user doing so is an
 administrator user).

 For the user who installed MySQL, it won't  cause problems. After you stop
 the service you can start

 mysqld --defaults-file=path\to\datadir\my.ini  --console

 from the non-elevated command line, with/without UAC. No file system
 virtualization will happen. That bug
 http://bugs.mysql.com/bug.php?id=38373  (user can not from mysqld from
 command line after installation) was  filed  by  myself  2.5 years ago , I
 could not leave that unfixed now.

 I know, writing to ProgramFiles might not be kosher,  but it works  if ACLs
 on our tree are set.  (And Microsoft should not tell people that writing to
 program files is bad, they are doing it  with SQLServer,  and also document
 it http://msdn.microsoft.com/en-us/library/ms143547.aspx , so we are again
 as good/bad as SQLServer here)

 2) There is no my.ini generated with a fresh install as far as I can see -
 so the server probably runs (it does!) with very low default buffer settings
 etc.  Also latin1 charset and MyISAM will be default.  I think a my.ini with
 settings fit for a 1GB-2GB RAM machine should be generated - and with a few
 configuration options.  And a my.ini will be required to solve 1) anyway.

 There is a my.ini, it is in database directory.


OK.. You moved my.ini to /datadir.  I only looked in installation folder
(where MySQL from Oracle has it). I now see it and also see the key defining
the service in registry reading ' C:\Program Files\MariaDB
5.2\bin\mysqld.exe --defaults-file=C:\Program Files\MariaDB
5.2\data\my.ini maria52' . So that is fine. My mistake.


 It is spartanic, it has port and datadir, nothing else. You can edit it
 using non-elevated notepad (with or without UAC) and there is a shortcut
  for it created in start menu, MariaDB 5.2 folder (rsp MariaDB 5.2 (x64) if
 for 64 bit package).

 There are zero performance related options, which means in fact it won't
 run on full speed. I have no strong opinion on it, nor I feel  qualified for
 configuring optimal performance out of the box .   If there is a strong
 demand on specific parameters, they should probably go there. I would like
 to hear more opinions on this, one thing that will definitely not be in the
 first incarnation of this installer is fully-featured ConfigWizard like
 stuff.

 Where I see differences between this my.ini and MySQL installer's default
 is

 * sql_mode (MySQL's default is  strict transactional tables)
 * default storage engine (MySQL default is innodb)
 * innodb buffer pool size (IIRC, MySQL's default is something like 12% of
 RAM)
 Those are trivial to change modifying my.ini

 Stuff like innodb log file size (calculated from innodb buffer pool size)
 not trivial to change with simple my.ini modification, there must be a clean
 shutdown and exiting files need to be removed.

  But still it is a good installer (and there is a 64 bit one as well), so
 this is an important step in the right direction.  So thanks for your
 effort!

 Thanks!

 -- Peter

 On Wed, Feb 2, 2011 at 14:37, Peter Laursen peter_laur...@webyog.com
 wrote:
 I am a little bit busy now, but will confirm tonight. -- Peter

 On Wed, Feb 2, 2011 at 14:12, Vladislav Vaintroub w...@montyprogram.com
 wrote:


 From: Peter Laursen [mailto:peter_laur...@webyog.com]
 Sent: Dienstag, 1. Februar 2011 20:31
 To: Vladislav Vaintroub
 Cc: maria-developers@lists.launchpad.net
 Subject: Re: [Maria-developers] Windows instller MWL#55 finished.
 It is a Danish Windows (Home Premium 64 bit).
 Hi Peter,
 As it turns out,  installer had the same localization problem registering
 service on German Windows.  Fixed  now,  I uploaded the msis to the same
 place http://cid-ff0c950417b4f8a4.office.live.com/browse.aspx/share

 Thanks,
 Wlad






___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Windows installer MWL#55 finished.

[Peter Laursen]

sorry .. it was 32 bit installer!

On Tue, Feb 1, 2011 at 18:43, Peter Laursen peter_laur...@webyog.comwrote:

 hmmm .. installer rolls back.  Why?

 64 bit build on 64 bit Win7 (UAC disabled). Default file path.  No
 conflicts with ports or service name specified.  After rollback there is no
 track left.


 -- Peter

 On Tue, Feb 1, 2011 at 18:05, Vladislav Vaintroub 
 w...@montyprogram.comwrote:



  -Original Message-
  From: Kristian Nielsen [mailto:kniel...@knielsen-hq.org]
  Sent: Dienstag, 1. Februar 2011 14:59
  To: Vladislav Vaintroub
  Cc: maria-developers@lists.launchpad.net; s...@askmonty.org; Michael
 Widenius
  Subject: Re: [Maria-developers] Windows installer MWL#55 finished.
 
  Vladislav Vaintroub w...@montyprogram.com writes:
 
   Wizard is an MFC application. I'm sorry for that, but my Windows C/C++
 GUI programming experience is not only rusty (prior to
 this
   WL last time I used it was more than  a decade ago), it is also
 restricted to MFC only. Being MFC application, it will require
 at
   least VS Professional to build.  There is no MFC in  free Visual
 Studio Express edition,  nor in free Windows SDK.  Build and
   packaging process will handle missing MFC gracefully (build won't try
 to compile upgrade wizard,  package won't include it , and
   installer won't  start it at the end of installation).
 
  What license are we distributing the wizard source code under?

  The reason I ask is that because of the above dependency, GPL may not be
  appropriate (and since it sounds like a new application, nor is it
  necessary). So we might consider another license, eg. BSD or if prefered
 some
  other more copy-left license. Or just GPL-with-MFC-exception.
 
  I don't really have an opinion myself for one license or the other, I
 just
  wanted to point out the issue to make sure it is considered by those
 that do
  care. Since it sounds like if we just use GPL, we may be releasing
 something
  that formally others cannot redistribute without violating the license.
 Which
  I think we should avoid, even if we're obviously not planning to sue
 anyone
  over it ...

 Not sure I'm correct person  to start discussions over the of GPL, I think
 I'm not qualified.

 I do know there is a plenty of established open source projects that use
 MFC, including GPLv2, such as different incarnations of
 Tortoise (SVN,CVS, BZR, HG).

 From my point of view,  it is just a  system library. It came bundled
 with compiler, just like other library CRT which is non-GPL
 that we use extensively for quite important functionality like strcpy() or
 say fopen().  Maybe this explanation will satisfy GPL
 purists. I do not think CRT , MFC , ATL (libraries that come bundled with
 Visual Studio) have any written license, at least I have
 never seen one. The source code is available, and installed together with
 Visual Studio.  If  one needs to redistribute one of this
 libraries  as DLLs, there is Microsoft EULA that basically allows
 inclusion into any software . But we do not even do that, as we
 link Visual Studio libraries (CRT, and also MFC now) statically, MySQL-ish
 way.

   - Kristian.


 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-developers] Windows installer MWL#55 finished.

[Peter Laursen]

Event Viewer has some info like 'Product: MariaDB 5.2 (x64) -- Installation
failed.' But nothing that can be used really. -- Peter

On Tue, Feb 1, 2011 at 18:54, Peter Laursen peter_laur...@webyog.comwrote:

 Same problem with 64 bit. Installation path, port and service name does not
 matter. i am not upgrading (path, port, service are all new). Rollback
 occurs after 'running install_mysql_db.exe' (or similar) occurs in the
 installer splash screen.

 -- Peter

 On Tue, Feb 1, 2011 at 18:45, Peter Laursen peter_laur...@webyog.comwrote:

 sorry .. it was 32 bit installer!


 On Tue, Feb 1, 2011 at 18:43, Peter Laursen peter_laur...@webyog.comwrote:

 hmmm .. installer rolls back.  Why?

 64 bit build on 64 bit Win7 (UAC disabled). Default file path.  No
 conflicts with ports or service name specified.  After rollback there is no
 track left.


 -- Peter

 On Tue, Feb 1, 2011 at 18:05, Vladislav Vaintroub w...@montyprogram.com
  wrote:



  -Original Message-
  From: Kristian Nielsen [mailto:kniel...@knielsen-hq.org]
  Sent: Dienstag, 1. Februar 2011 14:59
  To: Vladislav Vaintroub
  Cc: maria-developers@lists.launchpad.net; s...@askmonty.org; Michael
 Widenius
  Subject: Re: [Maria-developers] Windows installer MWL#55 finished.
 
  Vladislav Vaintroub w...@montyprogram.com writes:
 
   Wizard is an MFC application. I'm sorry for that, but my Windows
 C/C++ GUI programming experience is not only rusty (prior to
 this
   WL last time I used it was more than  a decade ago), it is also
 restricted to MFC only. Being MFC application, it will require
 at
   least VS Professional to build.  There is no MFC in  free Visual
 Studio Express edition,  nor in free Windows SDK.  Build and
   packaging process will handle missing MFC gracefully (build won't
 try to compile upgrade wizard,  package won't include it , and
   installer won't  start it at the end of installation).
 
  What license are we distributing the wizard source code under?

  The reason I ask is that because of the above dependency, GPL may not
 be
  appropriate (and since it sounds like a new application, nor is it
  necessary). So we might consider another license, eg. BSD or if
 prefered some
  other more copy-left license. Or just GPL-with-MFC-exception.
 
  I don't really have an opinion myself for one license or the other, I
 just
  wanted to point out the issue to make sure it is considered by those
 that do
  care. Since it sounds like if we just use GPL, we may be releasing
 something
  that formally others cannot redistribute without violating the
 license. Which
  I think we should avoid, even if we're obviously not planning to sue
 anyone
  over it ...

 Not sure I'm correct person  to start discussions over the of GPL, I
 think I'm not qualified.

 I do know there is a plenty of established open source projects that use
 MFC, including GPLv2, such as different incarnations of
 Tortoise (SVN,CVS, BZR, HG).

 From my point of view,  it is just a  system library. It came bundled
 with compiler, just like other library CRT which is non-GPL
 that we use extensively for quite important functionality like strcpy()
 or say fopen().  Maybe this explanation will satisfy GPL
 purists. I do not think CRT , MFC , ATL (libraries that come bundled
 with Visual Studio) have any written license, at least I have
 never seen one. The source code is available, and installed together
 with Visual Studio.  If  one needs to redistribute one of this
 libraries  as DLLs, there is Microsoft EULA that basically allows
 inclusion into any software . But we do not even do that, as we
 link Visual Studio libraries (CRT, and also MFC now) statically,
 MySQL-ish way.

   - Kristian.


 ___
 Mailing list: https://launchpad.net/~maria-developers
 Post to : maria-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~maria-developers
 More help   : https://help.launchpad.net/ListHelp





___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp