Re: PDBPLUS
| From: | Alan Knowles | Date: | Sun, 03 Feb 2002 04:22:28 +0000 |
| Subject: | Re: PDBPLUS | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-4362@lists.php.net to get a copy of this message | ||
mmh, why not try this in php-gtk,
I already started hacking something together as part of phpmole.. - uses peardb as the conneciton layer
* it is __slowly__ moving towards pear standards.. but since all php_gtk functions use underscore rather than studlycaps it inherited that formating.. - so it mixes the two a little...
- tree that expands the database -> databases/tables/items
- table that views the items - entryfield to edit the data.(although it doesnt update it)
todo:
the query builder could be a textbox with a popup listbox if any SQL keyword matches..
a visual database designer - would have to use the gtklayout widget...
the only problems I ran into where that database connections over tcpip dont tend to be encrypted..
there are a number of other people who have looked at php-gtk dbaccess, although alot of other efforts have missed the key components classes, glade and peardb.
regards
alan
ps. sorry thomas - that "reply to" got me again :)
Tomas V.V.Cox wrote:
"Tomas V.V.Cox" wrote:So let's go then :-) I'm going to start thinking on it and try to write some specs, and see how we can coordinate us.Here are the first ideas: Command name ------------ pdbplus (please propose others I think this is a little ugly) Comand line args ---------------- --dsn DSN (use to this database) -q "query" (launch this query and exit) -v level (0: quite, 1: information only, 2: full) --debug (debug mode) Export args: --dsnout DSN (export data to this database) --fileout filename (export data as SQL stmts to file) --table "table1, table2" (export only this tables) Import args: --dnsin DSN (import data from this database) -f or --filein filename (import/execute this file) Console options --------------- query_string (launch this query) \export export-args \import import-args \php (execute php code |1|) \h (help) \e (launch your editor |2|) \pager pager_opts (limit, count, pause, etc |3|) \dsn DSN (change database) \f filename (or Oracle way: @filename) \q (quit) \1..9 (save last query in postion |4|) \l (list stored queries) \auto on|off (set autocommit to on/off) \begin (start transaction) \end (end transaction) \roll (roll back transaction) \??? (|5|) 1..9 (execute stored query) ctrl+r (reverse search) up/down (up/down across the history) tab (complention of sql statements, table names, fields names?) ctrl+d (exit) Direct read commands from stdin support: cat filename | pdbplus pdbplus < filename Notes: |1| I'll came with the ideas on this more later |2| I don't know how we could do that if the editor is not an X app |3| That needs to be thinked yet |4| Something like "query bookmark" or stored procedures |5| Change database, list DB info (tables, views, databases, users), ... I'll start with the general interface and the readline stuff (hehe I've just compiled its support and wanna try it :-P) Tomas V.V.Cox