- developers - lists.mariadb.org

[Maria-developers] [Branch ~maria-captains/maria/5.1] Rev 2853: Removed extra } that caused script to fail with syntax error
by noreply＠launchpad.net 10 May '10

10 May '10

------------------------------------------------------------ revno: 2853 committer: Michael Widenius <monty(a)askmonty.org> branch nick: maria-5.1 timestamp: Mon 2010-05-10 21:23:16 +0300 message: Removed extra } that caused script to fail with syntax error modified: scripts/mysqld_multi.sh -- lp:maria https://code.launchpad.net/~maria-captains/maria/5.1 Your team Maria developers is subscribed to branch lp:maria. To unsubscribe from this branch go to https://code.launchpad.net/~maria-captains/maria/5.1/+edit-subscription

1 0

[Maria-developers] Windows installer
by Bo Thorsen 10 May '10

10 May '10

Hi everyone, I have been looking at getting our binary windows distribution back on track. One of the options would be to create the zip file like we did earlier. Another way would be to create a proper windows installer. For this, there are several options: NSIS, WIX, etc. I spent a bit of time investigating the CPack parts of CMake. And during the investigation, I managed to pretty much write an entire installer. It was quite easy. The way this works is to add INSTALL instructions in the CMakeFiles.txt, plus a bit of extra information for building the installer package. You can see this in the patch I have attached. With the patch applied, you have to install NSIS (http://nsis.sourceforge.net) and add it to the path. Build MariaDB in release, and run "cpack" in the MariaDB tree. It's NSIS based because this seems to be the one cpack works best with. The question is what direction to continue in. I'd appreciate some feedback on this, because I'm not certain if it's the right way to go. It has been pretty easy so far, so I'm pretty happy to continue with it. IMHO, the most important thing not implemented in this installer yet is to set up MariaDB as a service. I'm going to focus on getting Windows running in KVM for our buildbot system now. And then I'll get back to this later. Cheers, Bo Thorsen.

6 9

[Maria-developers] [Branch ~maria-captains/maria/5.1] Rev 2852: bugfix from mysql-5.1, apparently lost in a merge
by noreply＠launchpad.net 10 May '10

10 May '10

------------------------------------------------------------ revno: 2852 committer: Sergei Golubchik <sergii(a)pisem.net> branch nick: maria-5.1 timestamp: Mon 2010-05-10 16:23:08 +0200 message: bugfix from mysql-5.1, apparently lost in a merge modified: sql/sql_select.cc -- lp:maria https://code.launchpad.net/~maria-captains/maria/5.1 Your team Maria developers is subscribed to branch lp:maria. To unsubscribe from this branch go to https://code.launchpad.net/~maria-captains/maria/5.1/+edit-subscription

1 0

[Maria-developers] Updated (by Serg): innodb statistics in the slow log (115)
by worklog-noreply＠askmonty.org 10 May '10

10 May '10

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: innodb statistics in the slow log CREATION DATE..: Sun, 25 Apr 2010, 16:35 SUPERVISOR.....: Sergei IMPLEMENTOR....: COPIES TO......: CATEGORY.......: Server-BackLog TASK ID........: 115 (http://askmonty.org/worklog/?tid=115) VERSION........: Server-5.3 STATUS.........: Un-Assigned PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 0 (hours remain) ORIG. ESTIMATE.: 0 PROGRESS NOTES: -=-=(Serg - Mon, 10 May 2010, 14:36)=-=- Category updated. --- /tmp/wklog.115.old.7130 2010-05-10 14:36:08.000000000 +0000 +++ /tmp/wklog.115.new.7130 2010-05-10 14:36:08.000000000 +0000 @@ -1 +1 @@ -Server-Sprint +Server-BackLog -=-=(Serg - Mon, 10 May 2010, 14:36)=-=- Version updated. --- /tmp/wklog.115.old.7130 2010-05-10 14:36:08.000000000 +0000 +++ /tmp/wklog.115.new.7130 2010-05-10 14:36:08.000000000 +0000 @@ -1 +1 @@ -Server-9.x +Server-5.3 DESCRIPTION: We need to find some way for innoDB/XtraDB specific information to appear in the slow log. Same effect as in Percona patches, but a with cleaner implementation. ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

[Maria-developers] Updated (by Serg): innodb statistics in the slow log (115)
by worklog-noreply＠askmonty.org 10 May '10

10 May '10

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: innodb statistics in the slow log CREATION DATE..: Sun, 25 Apr 2010, 16:35 SUPERVISOR.....: Sergei IMPLEMENTOR....: COPIES TO......: CATEGORY.......: Server-BackLog TASK ID........: 115 (http://askmonty.org/worklog/?tid=115) VERSION........: Server-5.3 STATUS.........: Un-Assigned PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 0 (hours remain) ORIG. ESTIMATE.: 0 PROGRESS NOTES: -=-=(Serg - Mon, 10 May 2010, 14:36)=-=- Category updated. --- /tmp/wklog.115.old.7130 2010-05-10 14:36:08.000000000 +0000 +++ /tmp/wklog.115.new.7130 2010-05-10 14:36:08.000000000 +0000 @@ -1 +1 @@ -Server-Sprint +Server-BackLog -=-=(Serg - Mon, 10 May 2010, 14:36)=-=- Version updated. --- /tmp/wklog.115.old.7130 2010-05-10 14:36:08.000000000 +0000 +++ /tmp/wklog.115.new.7130 2010-05-10 14:36:08.000000000 +0000 @@ -1 +1 @@ -Server-9.x +Server-5.3 DESCRIPTION: We need to find some way for innoDB/XtraDB specific information to appear in the slow log. Same effect as in Percona patches, but a with cleaner implementation. ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

[Maria-developers] Updated (by Serg): insert ignore ha_extra hint (114)
by worklog-noreply＠askmonty.org 10 May '10

10 May '10

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: insert ignore ha_extra hint CREATION DATE..: Sun, 25 Apr 2010, 16:32 SUPERVISOR.....: Sergei IMPLEMENTOR....: COPIES TO......: CATEGORY.......: Server-BackLog TASK ID........: 114 (http://askmonty.org/worklog/?tid=114) VERSION........: Server-5.3 STATUS.........: Un-Assigned PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 0 (hours remain) ORIG. ESTIMATE.: 0 PROGRESS NOTES: -=-=(Serg - Mon, 10 May 2010, 14:35)=-=- Category updated. --- /tmp/wklog.114.old.7124 2010-05-10 14:35:59.000000000 +0000 +++ /tmp/wklog.114.new.7124 2010-05-10 14:35:59.000000000 +0000 @@ -1 +1 @@ -Server-Sprint +Server-BackLog -=-=(Serg - Mon, 10 May 2010, 14:35)=-=- Version updated. --- /tmp/wklog.114.old.7124 2010-05-10 14:35:59.000000000 +0000 +++ /tmp/wklog.114.new.7124 2010-05-10 14:35:59.000000000 +0000 @@ -1 +1 @@ -Server-9.x +Server-5.3 DESCRIPTION: There is HA_EXTRA_WRITE_CAN_REPLACE hint that tells the engine that the following ::write_row() calls are part of the REPLACE statement, not INSERT. With this knowledge the engine can execute the replace internally, deleting the conflicting row in the ::write_row() method instead of returning an error. We need a similar HA_EXTRA_WRITE_CAN_IGNORE hint to allow engines to optimize INSERT IGNORE in a similar way. ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

[Maria-developers] Updated (by Serg): insert ignore ha_extra hint (114)
by worklog-noreply＠askmonty.org 10 May '10

10 May '10

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: insert ignore ha_extra hint CREATION DATE..: Sun, 25 Apr 2010, 16:32 SUPERVISOR.....: Sergei IMPLEMENTOR....: COPIES TO......: CATEGORY.......: Server-BackLog TASK ID........: 114 (http://askmonty.org/worklog/?tid=114) VERSION........: Server-5.3 STATUS.........: Un-Assigned PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 0 (hours remain) ORIG. ESTIMATE.: 0 PROGRESS NOTES: -=-=(Serg - Mon, 10 May 2010, 14:35)=-=- Category updated. --- /tmp/wklog.114.old.7124 2010-05-10 14:35:59.000000000 +0000 +++ /tmp/wklog.114.new.7124 2010-05-10 14:35:59.000000000 +0000 @@ -1 +1 @@ -Server-Sprint +Server-BackLog -=-=(Serg - Mon, 10 May 2010, 14:35)=-=- Version updated. --- /tmp/wklog.114.old.7124 2010-05-10 14:35:59.000000000 +0000 +++ /tmp/wklog.114.new.7124 2010-05-10 14:35:59.000000000 +0000 @@ -1 +1 @@ -Server-9.x +Server-5.3 DESCRIPTION: There is HA_EXTRA_WRITE_CAN_REPLACE hint that tells the engine that the following ::write_row() calls are part of the REPLACE statement, not INSERT. With this knowledge the engine can execute the replace internally, deleting the conflicting row in the ::write_row() method instead of returning an error. We need a similar HA_EXTRA_WRITE_CAN_IGNORE hint to allow engines to optimize INSERT IGNORE in a similar way. ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

[Maria-developers] Updated (by Serg): support many clustered keys per table (113)
by worklog-noreply＠askmonty.org 10 May '10

10 May '10

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: support many clustered keys per table CREATION DATE..: Sun, 25 Apr 2010, 16:23 SUPERVISOR.....: Sergei IMPLEMENTOR....: COPIES TO......: CATEGORY.......: Server-BackLog TASK ID........: 113 (http://askmonty.org/worklog/?tid=113) VERSION........: Server-5.3 STATUS.........: Un-Assigned PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 0 (hours remain) ORIG. ESTIMATE.: 0 PROGRESS NOTES: -=-=(Serg - Mon, 10 May 2010, 14:35)=-=- Category updated. --- /tmp/wklog.113.old.7118 2010-05-10 14:35:50.000000000 +0000 +++ /tmp/wklog.113.new.7118 2010-05-10 14:35:50.000000000 +0000 @@ -1 +1 @@ -Server-Sprint +Server-BackLog -=-=(Serg - Mon, 10 May 2010, 14:35)=-=- Version updated. --- /tmp/wklog.113.old.7105 2010-05-10 14:35:25.000000000 +0000 +++ /tmp/wklog.113.new.7105 2010-05-10 14:35:25.000000000 +0000 @@ -1 +1 @@ -Server-9.x +Server-5.3 DESCRIPTION: The server now assumes that there can be only one clustered key per table, and only primary key can be clustered. It's not true for certain storage engines, we need to remove this limitation ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

[Maria-developers] Updated (by Serg): support many clustered keys per table (113)
by worklog-noreply＠askmonty.org 10 May '10

10 May '10

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: support many clustered keys per table CREATION DATE..: Sun, 25 Apr 2010, 16:23 SUPERVISOR.....: Sergei IMPLEMENTOR....: COPIES TO......: CATEGORY.......: Server-BackLog TASK ID........: 113 (http://askmonty.org/worklog/?tid=113) VERSION........: Server-5.3 STATUS.........: Un-Assigned PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 0 (hours remain) ORIG. ESTIMATE.: 0 PROGRESS NOTES: -=-=(Serg - Mon, 10 May 2010, 14:35)=-=- Category updated. --- /tmp/wklog.113.old.7118 2010-05-10 14:35:50.000000000 +0000 +++ /tmp/wklog.113.new.7118 2010-05-10 14:35:50.000000000 +0000 @@ -1 +1 @@ -Server-Sprint +Server-BackLog -=-=(Serg - Mon, 10 May 2010, 14:35)=-=- Version updated. --- /tmp/wklog.113.old.7105 2010-05-10 14:35:25.000000000 +0000 +++ /tmp/wklog.113.new.7105 2010-05-10 14:35:25.000000000 +0000 @@ -1 +1 @@ -Server-9.x +Server-5.3 DESCRIPTION: The server now assumes that there can be only one clustered key per table, and only primary key can be clustered. It's not true for certain storage engines, we need to remove this limitation ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

[Maria-developers] Updated (by Serg): support many clustered keys per table (113)
by worklog-noreply＠askmonty.org 10 May '10

10 May '10

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: support many clustered keys per table CREATION DATE..: Sun, 25 Apr 2010, 16:23 SUPERVISOR.....: Sergei IMPLEMENTOR....: COPIES TO......: CATEGORY.......: Server-Sprint TASK ID........: 113 (http://askmonty.org/worklog/?tid=113) VERSION........: Server-5.3 STATUS.........: Un-Assigned PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 0 (hours remain) ORIG. ESTIMATE.: 0 PROGRESS NOTES: -=-=(Serg - Mon, 10 May 2010, 14:35)=-=- Version updated. --- /tmp/wklog.113.old.7105 2010-05-10 14:35:25.000000000 +0000 +++ /tmp/wklog.113.new.7105 2010-05-10 14:35:25.000000000 +0000 @@ -1 +1 @@ -Server-9.x +Server-5.3 DESCRIPTION: The server now assumes that there can be only one clustered key per table, and only primary key can be clustered. It's not true for certain storage engines, we need to remove this limitation ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0