Hello,
Just got this interesting mail from Stefano.
I guess it's better if we discuss that on this list...
I think the idea is fine, but also that we _first_ should finish the 2.2.0 release before working on any new (even if cool) feature. Otherwise we will have rc5, rc6, ... rc99 like the linux kernel :)
Comments welcome! Swix, going back to school work (preparing exams)
----- Forwarded message from Stefano Locati locati@users.sourceforge.net -----
Subject: proposal From: Stefano Locati locati@users.sourceforge.net Date: Fri, 10 Aug 2001 04:07:46 -0700
i'm a user of phpMyAdmin since long time and i'm seeing it improving and getting better and better.
i've an idea about a future feature that i need and that i would develop myself and also share with others.
it's about db documentation. i'm working on many websites projects and keeping an uptodate db documentation is a problem. i don't want to use commercial tools like the good power designer. what i would like is something very simple in phpmyadmin style.
i would add another link after the common browse - select - insert. A documentation link that would allow any person to write information about the db tables and fields.
the next step would be info about relationship. this information would be stored in three db tables. i would add a button to create those tables in the case they were not detected in the current db. the metaschema of the db would be extracted giving the possibility to just click side of a field / table to document it.
i would work on a cvs copy without committing until the software isn't good enough for at least a test drive. i've experience with php and cvs.
the tables i would add would be something like:
sch_table(name, description) sch_field(name, tablename, description) sch_relationship(name1, tablename1, name2, tablename2, description)
what do you think about this? i'm open to start a discussion phase with members of this project about the willingness to include such feature, and how to do it.
bye and keep up with the good work stefano
----- End forwarded message -----
Hey all.
I think the idea is fine, but also that we _first_ should finish the 2.2.0 release before working on any new (even if cool) feature. Otherwise we will have rc5, rc6, ... rc99 like the linux kernel :)
Comments welcome!
I agree. I think it would be a very nice feature and I agree on putting it on the TODO/Wish list but that we forget about it until after the 2.2.0 release.
Further I think this might as for some considerations on splitting phpMyAdmin into modules (for a future version 3.x.x series) - making it easy to append new features (and for new users to append their own modules) - but also minimizing the system/software requrements for the running of a basic phpMyAdmin without all the fancy features/modules.
Because the more advanced phpMyAdmin get's - the more difficult to use it gets and the security-issues just gets larger and larger. So it might be very nice for ISP (etc.) to be able to disable specific features/modules.
This way - we would also have a basic phpMyAdmin core that woulden't need to be serious tested every time a new feature/module is added/changed - making it more efficienent to test specific features/modules.
Comments on this is appreciated? ;o)))
Have a nice weekend.
-- Kind regards Geert Lund
On Fri, 10 Aug 2001, Geert Lund - SilverSoft Productions wrote:
I agree. I think it would be a very nice feature and I agree on putting it on the TODO/Wish list but that we forget about it until after the 2.2.0 release.
Put it on the Feature list on SourceForge
Because the more advanced phpMyAdmin get's - the more difficult to use it gets and the security-issues just gets larger and larger. So it might be very nice for ISP (etc.) to be able to disable specific features/modules.
I would even like to disable some features/modules per user on my system.
This way - we would also have a basic phpMyAdmin core that woulden't need to be serious tested every time a new feature/module is added/changed - making it more efficienent to test specific features/modules.
That would be a definate way to speed up development in the long term, but we would have to make sure that we get the module/plugin system perfect before trying to add things to it, definetly a 3.x feature level item.
-
Geert Lund - SilverSoft Productions -
Olivier M. -
Robin Johnson