Re: [Maria-developers] mysql 5.6, 5.7

it's a nice feature not a must have feature trace what mariadb is doing in optimizer, some time (in bugs or performace problem) is nice to see what is going wrong, and why a must have feature, for me, is lock partition prune i have many myisam table with lock problem and partition lock prune can s

[Maria-developers] review / close MDEV-4581

hi guys, could review / close MDEV-4581 ? -- Roberto Spadim ___ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net

Re: [Maria-developers] mysql 5.6, 5.7

+1 on the optimizer tracing. I have found it useful. We've had a couple of instances where we looked at where an InnoDB query plan and TokuDB query plan diverge for some query, and it showed us bugs in our engine. Just my $.02. -Zardosht On Mon, Jun 17, 2013 at 10:37 PM, Igor Babaev wrote: > On

Re: [Maria-developers] mysql 5.6, 5.7

On 06/17/2013 04:24 PM, Roberto Spadim wrote: > hi guys, i was reading mysql 5.6 and 5.7 manual > i know that mariadb is very different (a bit) than mysql internally > there's a mysql merge issue or something like that i can see what will > be merged and what not? > > i like the partition lock pru

[Maria-developers] Implementing implicit primary key in mysql server

Hi, As we know, InnoDB has implicit primary key if a table hasn't defined a primary key. However MySQL server doesn't know this primary key, so this primary key will not apear in binlog. When we are using ROW format binlog for replication, if a table has no any indexes, that's a disaster. If a ta

[Maria-developers] query cache issue

guys, i sent some (many) MDEV issues to have a better control over query cache i want to comment here to don't stay with this idea in my mind only... i created some labels in JIRA: querycache - relative to query cache qc_info - relative to qc_info plugin querycache_client - relative to implement q

[Maria-developers] mysql 5.6, 5.7

hi guys, i was reading mysql 5.6 and 5.7 manual i know that mariadb is very different (a bit) than mysql internally there's a mysql merge issue or something like that i can see what will be merged and what not? i like the partition lock prune, memcache and optimizer tracer of mysql 5.6, but today

[Maria-developers] close some mdev

hi guys could anyone close some opened and fixed (won't fix) mdev's ? the comment explain why to close it 1. MDEV-4571 1. MDEV-4583 1. MDEV-4589

Re: [Maria-developers] [GSoC] Kerberize MariaDB -- some unclear point about the project

>From: Maria-developers [mailto:maria-developers-bounces+wlad=montyprogram@lists.launchpad.net] On Behalf Of QIU Shuang >Sent: Sonntag, 16. Juni 2013 16:07 >To: Vladislav Vaintroub; maria-developers@lists.launchpad.net >Subject: [Maria-developers] [GSoC] Kerberize MariaDB -- some unclear poin

Re: [Maria-developers] Jira new field

ok =) thanks 2013/6/17 Sergei Golubchik > Hi, Roberto! > > On Jun 17, Roberto Spadim wrote: > > > > today i'm 'working around ' this, and putting the 'group information' in > > MDEV issue, example.. query cache things i put > > QUERY CACHE - some issue title > > processlist things i put > > PRO

Re: [Maria-developers] Jira new field

sorry many emails... today i'm 'working around ' this, and putting the 'group information' in MDEV issue, example.. query cache things i put QUERY CACHE - some issue title processlist things i put PROCESSLIST - some issue title this works too, but well. mariadb team can change and when i lost my

Re: [Maria-developers] Jira new field

it don't need to be a very big field (100bytes of latin1 is nice to me) 2013/6/17 Roberto Spadim > i think that the right way (but it's not good to me...) > is build a issue tracker outside jira just to me > but i'm using mariadb php and apache, and i only have issues in mariadb > (ok i have so

Re: [Maria-developers] Jira new field

i think that the right way (but it's not good to me...) is build a issue tracker outside jira just to me but i'm using mariadb php and apache, and i only have issues in mariadb (ok i have some mysql issues but i don't use it anymore) maybe add a field for example 'reporter private field' just to a

Re: [Maria-developers] Jira new field

heeh sometimes i just add a label that don't have interest to mariadb team, it's just to 'group' my issues if there's a interesting and nice way to do this could be nice it's just to organize my issues and when i have time see what changed and where, not changing the work of mariadb placing the rig

[Maria-developers] Jira new field

hi guys, could we add a Reporter Label inside jira issue? instead of only Label (used by mariadb team) it's easier to filter issues, thinking about the reporter filter not for mariadb team filters -- Roberto Spadim ___ Mailing list: https://launchpad.ne