Re: [Phpmyadmin-devel] [Phpmyadmin-cvs] DisableIS in phpMyAdmin-trunk-20080424-022001 doesn't work
25 Apr
2008
25 Apr
'08
1:14 a.m.
Hi,
Rekrutacja schrieb:
i've tested latest pma
(phpMyAdmin-trunk-20080424-022001), and it seems
it has DisableIS set to true as default, but when i log in and click any
of the tables from database, i can see this on the server:
SELECT TRIGGER_SCHEMA, TRIGGER_NAME, EVENT_MANIPULATION, ACTION_TIMING,
ACTION_STATEMENT, EVENT_OBJECT_SCHEMA, EVENT_OBJECT_TABLE FROM
information_schema.TRIGGERS WHERE EVENT_OBJECT_SCHEMA= 'test99_db' and
EVENT_OBJECT_TABLE = 'phpbb2_bookmarks'
and is taking very long time, same as without DisableIS.
does DisableIS is not yet fully implemented or is it a bug?
1. not fully implemented
2. IMHO sooner, later or already SHOW will mapped to I_S
3. the above statement should include TRIGGER_SCHEMA in WHERE
Marc?
was there any reason not including TRIGGER_SCHEMA in WHERE?
--
Sebastian Mendel
25 Apr
25 Apr
8:27 a.m.
New subject: [Phpmyadmin-devel] [Phpmyadmin-cvs] DisableIS in
Sebastian Mendel a écrit :
Hi,
Rekrutacja schrieb:
I'll check about this.
i've tested latest pma
(phpMyAdmin-trunk-20080424-022001), and it seems
it has DisableIS set to true as default, but when i log in and click any
of the tables from database, i can see this on the server:
SELECT TRIGGER_SCHEMA, TRIGGER_NAME, EVENT_MANIPULATION, ACTION_TIMING,
ACTION_STATEMENT, EVENT_OBJECT_SCHEMA, EVENT_OBJECT_TABLE FROM
information_schema.TRIGGERS WHERE EVENT_OBJECT_SCHEMA= 'test99_db' and
EVENT_OBJECT_TABLE = 'phpbb2_bookmarks'
and is taking very long time, same as without DisableIS.
does DisableIS is not yet fully implemented or is it a bug?
1. not fully implemented
2. IMHO sooner, later or already SHOW will mapped to I_S
3. the above statement should include TRIGGER_SCHEMA in WHERE
Marc?
was there any reason not including TRIGGER_SCHEMA in WHERE?
26 Apr
26 Apr
11:23 a.m.
New subject: [Phpmyadmin-devel] [Phpmyadmin-cvs] DisableIS in
Sebastian Mendel a écrit :
Hi,
Rekrutacja schrieb:
The EVENT_OBJECT_SCHEMA seems to always have the same content as
TRIGGER_SCHEMA, but I just noticed that in the MySQL manual they suggest
using TRIGGER_SCHEMA in the WHERE clause as you suggested, so I merged
the change and the doc reference (for version 2.11.7)
http://phpmyadmin.svn.sourceforge.net/viewvc/phpmyadmin/branches/QA_2_11/ph…
Rekrutacja, is it faster this way on your server?
i've tested latest pma
(phpMyAdmin-trunk-20080424-022001), and it seems
it has DisableIS set to true as default, but when i log in and click any
of the tables from database, i can see this on the server:
SELECT TRIGGER_SCHEMA, TRIGGER_NAME, EVENT_MANIPULATION, ACTION_TIMING,
ACTION_STATEMENT, EVENT_OBJECT_SCHEMA, EVENT_OBJECT_TABLE FROM
information_schema.TRIGGERS WHERE EVENT_OBJECT_SCHEMA= 'test99_db' and
EVENT_OBJECT_TABLE = 'phpbb2_bookmarks'
and is taking very long time, same as without DisableIS.
does DisableIS is not yet fully implemented or is it a bug?
1. not fully implemented
2. IMHO sooner, later or already SHOW will mapped to I_S
3. the above statement should include TRIGGER_SCHEMA in WHERE
Marc?
was there any reason not including TRIGGER_SCHEMA in WHERE?
5985
days inactive
5986
days old
2 comments
2 participants
participants (2)
-
Marc Delisle -
Sebastian Mendel