On Tue, Jan 12, 1999 at 09:34:41PM -0800, Pann McCuaig wrote: > > Does it make much sense to have a generic gui frontend to an SQL db? > > Usually you would want something specific to your database/application. > > Ah, here's a difference between the Pee-Cee world and the *nix world > where there's something to be said for the "other place." > > It's really handy to be able to take a quick look at a database to see > what the structure is like, how many tables, how many records, etc., > etc.
[6:26pm] [EMAIL PROTECTED]:/usr/doc/mysql-manual/html> mysql rising Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 2863 to server version: 3.21.31 Type 'help' for help. mysql> describe releases; +-------------+----------+------+-----+------------+-------+ | Field | Type | Null | Key | Default | Extra | +-------------+----------+------+-----+------------+-------+ | version | char(50) | | | | | | releasedate | date | | | 0000-00-00 | | | program | char(50) | | | | | +-------------+----------+------+-----+------------+-------+ 3 rows in set (0.00 sec) mysql> quit Bye So I had to look it up, but that's because I do SQL work a few times a year at most. A GUI might be nice occasionally but is only (to me) useful for bootstrapping a custom interface, which is what should really be deployed. That's something like 90% of the audience for Delphi and Visual Basic -- quick and dirty DB frontends. Hamish -- Hamish Moffatt VK3TYD [EMAIL PROTECTED], [EMAIL PROTECTED] Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5 CCs of replies from mailing lists are welcome. http://hamish.home.ml.org
