Uhm, this isn't really true. Suppose you're developing an application. You're either going to be creating the underlying table structure (or actually the entire ER for the database) or you're going to need to see what the database structure actually looks like.
If you take the approach of using struts/hibernate as your OO to RDBMS mapping, you're going to lose out on what an RDBMS can do beyond being a "persistence" layer. Most likely, you're writing an app/applet/servelet/whatever against an existing database so you're going to want to see how the data is laid out and some of the underlying structure. You're also going to want to know how to create your queries to take advantage of the existing indexes or to create new ones. (Performance tuning.) A stand alone GUI tool would be nice, however, that means I have to leave one app (my IDE) and switch to a different tool. Just my .02 cents. But hey! What do I know? Its not like I've been doing app development AND database design for over 20 years.... ;-) -G -----Original Message----- From: Veaceslav Chicu [mailto:[EMAIL PROTECTED] Sent: Friday, January 27, 2006 10:04 AM To: Derby Discussion Subject: Re: Developing a UI for Derby how much non programmers look directly in derby? derby is a tool for programmers, programmers are users of derby (see their applications) users use applications no need for a derby specific gui, derby expose SQL and jdbc interface, which are standard best regards, Slavic Andrus Adamchik wrote: > I'd say go with standalone as well. It makes sense because Derby itself > is a database, not a development framework, so there is a good chance > that many potential users of the GUI won't be IDE users at all. > > Andrus > > > On Jan 27, 2006, at 10:33 AM, Manyi Lu wrote: >> A GUI for derby is a great idea. I have used SquirreL, but it lacks >> some functionality, and it is under LGPL not Apache license. >> >> A stand alone GUI would be better, people tend to use different IDEs. >> >> Manyi >> >> >> duminda wrote: >> >>> Hi, >>> What does the community most wanted, Eclipse or Stand alone?. >>> Duminda >>> >>> >>> ----- Original Message ----- >>> From: Satheesh Bandaram >>> To: Derby Discussion >>> Sent: Friday, January 27, 2006 12:59 PM >>> Subject: Re: Developing a UI for Derby >>> >>> Sounds nice. Derby doesn't have its own GUI. This page at Apache >>> Derby lists several known GUI tools that work with Derby. Are you >>> thinking of a stand-alone tool or on some framework... like Eclipse? >>> >>> http://db.apache.org/derby/integrate/misc.html#Products+by+Type >>> >>> Satheesh >>> >>> duminda wrote: >>> >>>> Hi, >>>> I'm interested in developing a GUI for Derby with Apache >>>> licence. >>>> Schema browser >>>> alter table (column/constraint) >>>> DML (insert/delete/update) >>>> This will be something like "Toad" to "Oracle". >>>> Is there any tool already exist? >>>> Regards! >>>> Duminda >>>> >>> >>> >> >> >> > >
