Folks Back in Sep 2000 I released a pure Perl program, then called myadmin.pl, for administration of MySQL dbs. See tut # 35:
http://savage.net.au/Perl-tutorials.html Here are the features: # Operating System-level features # o Runs under Linux # o Runs under Windows NT, just by changing the she-bang line above # Perl-level features: # o Runs under -T # o Runs under $ENV{'PATH'} = ''; # Database-level features: # o Create database # o Drop database # o Backup database via browser download # o Restore database # o Display on 1 page the schema, ie column attributes, of all tables # Table-level features # o Create table # o Drop table # o Backup table via browser download # o Restore table # o Rename table # o Display table schema, ie column and index attributes # o 1-click Select * # o 1-click Equi-join (assumes 1:1 relationship between tables) # o Display all foreign keys, here defined as columns with the same # name in 2 or more tables. This feature makes my previous # program in this area - myschema.pl, in tutorial # 27 - obsolete. # All foreign keys are linked with hrefs, so by clicking on a key # in table A you are taken to the definition of any other table B # which has a column of the same name # Index-level features # o Create index # o Drop index # Column-level features # o Add column # o Drop column # o Rename column # o Edit column attributes # o 1-click list all column attributes & cross-check them (different tables, same column name). # Assumes 2 columns with the same name, in different tables!, are meant to be the same. # SQL-level features # o Run any SQL command # I am planning a new version (V 2), which will be based on ODBC or Matt Sergeant's clever package DBIx::AnyDBD. The latter would allow db vendor-specific code at any point to override the default, db vendor-independent, behaviour. I will probably incorporate my color-coded schema diff program mydiff.pl. See tut # 26: http://savage.net.au/Perl-tuts-1-30.html If you have any ideas, let me know, preferably via the list. Here are the constraints: o A CGI script o Web server-independent o OS-independent o Db vendor-independent o Pure Perl, although of course it may use compiled DB* modules o Support basic admin features as above. Ie no need (yet) to support triggers, stored procedures, etc. Another way of saying this is: Forget featuritis. The current list of features is all I'm aiming at in V 2 o Output will be based on CSS and V 2 of my module CGI::Explorer (V 2 to be released RSN [Real Soon Now, in case you have not seen that acronym before]) The motivation for this is that I will very soon need myadmin.cgi to support MySQL and Postgres, and perhaps MS Access (shudder), simultaneously. In particular I'm looking for _useful_ docs on ODBC. I've roamed around MS's site (watch wrap): http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/ htm/odbcsqltables.asp but that does not really tell me what I need to know. -- Cheers Ron Savage, [EMAIL PROTECTED] on 06/01/2003 http://savage.net.au/index.html
