Hi all,
I have a quick question about the "Support for procedures" project for Gsoc.
Since the events and triggers are available on a per table basis, I though that it would make sense to also have an overview of all the triggers and events that are available for a particular database. And then use links from the items from this overview to the listings of the triggers and events for the relevant table.
If it's a good idea, then I wonder where would the best place to access these lists. I think that it might make little sense to add more tabs to the menu that is displayed in a database page, as it is already quite crowded there. So how about a link to this feature from within a table-wise list of events/triggers? I guess that the workflow may be odd then: database -> table -> table events -> database events -> table events -> chosen item.
What do you think?
Thanks for any feedback.
Rouslan
Hi
Dne Wed, 6 Apr 2011 06:38:34 -0500 Rouslan Placella rouslan@placella.com napsal(a):
I have a quick question about the "Support for procedures" project for Gsoc.
Since the events and triggers are available on a per table basis, I though that it would make sense to also have an overview of all the triggers and events that are available for a particular database. And then use links from the items from this overview to the listings of the triggers and events for the relevant table.
Might be useful.
If it's a good idea, then I wonder where would the best place to access these lists. I think that it might make little sense to add more tabs to the menu that is displayed in a database page, as it is already quite crowded there. So how about a link to this feature from within a table-wise list of events/triggers? I guess that the workflow may be odd then: database -> table -> table events -> database events -> table events -> chosen item.
I think it's okay to add single tab with procedures/events/triggers there.
We might also use navigation frame for this...
I think it's okay to add single tab with procedures/events/triggers there.
We might also use navigation frame for this...
What do you think about a tab for routines and one for triggers/events? Events really are just triggers set to fire at a given time...
Oh, and could you please explain to me what you mean by 'use the navigation frame for this'?
Rouslan
Rouslan Placella a écrit :
I think it's okay to add single tab with procedures/events/triggers there.
We might also use navigation frame for this...
What do you think about a tab for routines and one for triggers/events? Events really are just triggers set to fire at a given time...
Oh, and could you please explain to me what you mean by 'use the navigation frame for this'?
This is the left-side frame where database and table names appear, with phpMyAdmin logo on top. If you look at the HTML source code, you'll see a frameset and this frame is named "frame_navigation".
On Wed, 2011-04-06 at 20:56 -0400, Marc Delisle wrote:
Rouslan Placella a écrit :
I think it's okay to add single tab with procedures/events/triggers there.
We might also use navigation frame for this...
What do you think about a tab for routines and one for triggers/events? Events really are just triggers set to fire at a given time...
Oh, and could you please explain to me what you mean by 'use the navigation frame for this'?
This is the left-side frame where database and table names appear, with phpMyAdmin logo on top. If you look at the HTML source code, you'll see a frameset and this frame is named "frame_navigation".
Thanks, I see what the navigation frame is, but I'm not sure how it could be useful for routines/events/triggers. Is it by displaying a small summary in the context of the other, main, frame? Thanks.
Rouslan
Hi
Dne Thu, 07 Apr 2011 10:08:58 +0100 Rouslan Placella rouslan@placella.com napsal(a):
Thanks, I see what the navigation frame is, but I'm not sure how it could be useful for routines/events/triggers. Is it by displaying a small summary in the context of the other, main, frame? Thanks.
All things could be listed there as well. For example phpPgAdmin does that:
http://phppgadmin.sourceforge.net/doku.php?id=screenshot_table_structure
I think it's okay to add single tab with procedures/events/triggers there.
We might also use navigation frame for this...
-- Michal Čihař | http://cihar.com | http://blog.cihar.com
I think we can take great advantage of the navigation frame. Sorry, I was late to notice about it.
We can ajaxify the navigation frame. 1. As a user selects a database, we can place the stored routines and events link. 2. As sometimes there may be a lots of tables in a database, I propose to create a tree view of routines, events, tables. 3. For triggers we can load a new link (triggers) as a user selects a table name.
Please suggest your view so that I can make changes to my proposal before the deadline.
Samiran Raj Boro Institute of Science and Technology Gauhati University Guwahati, Assam India
SF.net: srajbr IRC nickname: samiran
Hi
Dne Thu, 7 Apr 2011 11:08:31 +0530 Samiran Raj Boro srajbr@gmail.com napsal(a):
I think it's okay to add single tab with procedures/events/triggers there.
We might also use navigation frame for this...
-- Michal Čihař | http://cihar.com | http://blog.cihar.com
I think we can take great advantage of the navigation frame. Sorry, I was late to notice about it.
We can ajaxify the navigation frame.
- As a user selects a database, we can place the stored routines and events
link. 2. As sometimes there may be a lots of tables in a database, I propose to create a tree view of routines, events, tables. 3. For triggers we can load a new link (triggers) as a user selects a table name.
Yes, this definitely needs to be dynamic, because loading all the data at once would take too long.
-
Marc Delisle -
Michal Čihař -
Rouslan Placella -
Samiran Raj Boro