Can we expect to see MySQL in NB soon?

[philvh]

Some parts of this message have been removed. Learn more about Nabble's security policy.

There should be no debate for bundling whatsoever if:

1) Netbeans provides first class support for all major databases
2) Install MySQL is as easy as eating a piece of cake.

So, this is what needs to be done, if any:

1) Make Netbeans provides first class support for all major databases
2) Make installing MySQL is as easy as eating a piece of cake.

----- Original Message ----
From: Na'Tosha Dover <natosha@...>
To: nbusers@...
Sent: Saturday, January 19, 2008 10:54:38 AM
Subject: Re: [nbusers] Can we expect to see MySQL in NB soon?

Greetings Everyone,

My personal opinion is that NetBeans doesn't need to bundle an entire database bundled with it.  I think good support for working with many databases should be the goal.  Bundling a database with NetBeans is only going to be helpful for the percentage of NetBeans users who 1) use databases (currently I work on a large, stand-alone, end-user spectroscopy application  that does not utilize a database of any kind), and 2) can and want to use whatever database is bundled with the IDE (at my last job when I was writing Java web applications, I didn't get to make choices about which databases were used.  Either our clients made that choice for us, or the applications that were already in development when I got their had their own databases already created).  If you're not in one of these two groups, having a bundled database with the IDE is just going to mean a more bloated download.

Just my $0.02.

Na'Tosha

On Jan 18, 2008 3:24 PM, David Van Couvering <david@...> wrote:

Holy schmoly!  Quite a lot of opinions here!  It's great to see so
much passion and interest in databases and NetBeans!  Full disclosure:
I'm the Sun employee currently responsible for core database tooling
in NetBeans (e.g. the Database Explorer and Java DB support).

I personally don't think it's a good idea to bundle MySQL with
NetBeans.   If you've noticed, we actually don't bundle Java DB.  We
do detect it if it's on your system, either the one that's bundled in
JDK 6 or the one bundled in Glassfish (which *is* bundled with the
enterprise version of NetBeans).

There are a lot of other interesting ideas out there.  You're not the
only one asking me what we should do here or providing opinions.  I've
had a very busy last few days :)

I hope to gather up all your ideas, put them into some kind of
reasonable form, and get your votes on what we should be doing.  So
please send your ideas my way.

First step; let's brainstorm on ideas.  Send them to me, and not just
nbusers, or I may miss them.  I'll add them to the Wiki.  Or you can
add them directly to the Wiki.

We'll go from there.  I think database tooling for NetBeans just got a
little kick in the pants :)

David

P.S. For more on this please see
http://davidvancouvering.blogspot.com/2008/01/netbeans-and-mysql-what-to-do.html

On Jan 17, 2008 10:33 AM,  <darrinps@...> wrote:
> Are there any plans to ship NetBeans with MySQL instead of JavaDB (which I have had...well...a fair share of problems with over the last few years) now that Sun is planning to buy MySQL?
>
> If not bundled, will it at least have better out of the box support (come with the MySQL driver, etc.)?
>
>
>
>

--
David W. Van Couvering
http://davidvancouvering.blogspot.com

---

Looking for last minute shopping deals? Find them fast with Yahoo! Search.

[Briggs]

I'll chime in and sa NO to bundling MySQL with Netbeans.  The nice
thing, and the reason for, Derby (JavaDB) is that it is extremely
small, lightweight, and now part of the JDK. It gives developers the
ability to get to work on writing applications that rely on a JDBC
capable relational database.  This was a piece missing from the JDK.
Most of use probably rely on a back end relational database for
development and testing.  So, this was an extremely nice addition to
making development easier on us.

The magic of JDBC is it's extremely wonderful abstraction database
connectivity.  What could bundling MySQL do for most people?  Not
much.  Plus, now you have added so many extra platform dependency
problems and extreme bloat.  Which version would you package?  With
JavaDB we developers don't have to worry about it when just trying to
get their development environment up and running.

I would just add a plugin option that allows for the driver and
default parameters for connecting to a mysql db.  Perhaps people could
contribute scripts to start and stop it.  But, for me, that is about
it. That is all you need.  Download MySQL yourself and connect to it.
Plus, who wants the freakin' flame war of MySQL vs. Postgres vs.
Firebird vs. whatever.

I would also agree that bundling the container is a good thing.  It's
an implementation of a a spec many of us rely on; just like JavaDB.

Plus, isn't is super easy to package up a working copy of your application now?

Briggs.

[Briggs]

I just realized that NB does come with the drivers for mysql and
postres also, so I am happy with that.  :-)

On Jan 19, 2008 12:27 PM, Briggs <acidbriggs@...> wrote:

> I'll chime in and sa NO to bundling MySQL with Netbeans.  The nice
> thing, and the reason for, Derby (JavaDB) is that it is extremely
> small, lightweight, and now part of the JDK. It gives developers the
> ability to get to work on writing applications that rely on a JDBC
> capable relational database.  This was a piece missing from the JDK.
> Most of use probably rely on a back end relational database for
> development and testing.  So, this was an extremely nice addition to
> making development easier on us.
>
> The magic of JDBC is it's extremely wonderful abstraction database
> connectivity.  What could bundling MySQL do for most people?  Not
> much.  Plus, now you have added so many extra platform dependency
> problems and extreme bloat.  Which version would you package?  With
> JavaDB we developers don't have to worry about it when just trying to
> get their development environment up and running.
>
> I would just add a plugin option that allows for the driver and
> default parameters for connecting to a mysql db.  Perhaps people could
> contribute scripts to start and stop it.  But, for me, that is about
> it. That is all you need.  Download MySQL yourself and connect to it.
> Plus, who wants the freakin' flame war of MySQL vs. Postgres vs.
> Firebird vs. whatever.
>
> I would also agree that bundling the container is a good thing.  It's
> an implementation of a a spec many of us rely on; just like JavaDB.
>
> Plus, isn't is super easy to package up a working copy of your application now?
>
> Briggs.
>

--
"Conscious decisions by conscious minds are what make reality real"

[Sean Carrick]

I didn't know that...where did you find them?

Cheers,

Sean Carrick
PekinSOFT Systems
PekinSOFT@...

On Jan 19, 2008 5:42 PM, Briggs < acidbriggs@...> wrote:

I just realized that NB does come with the drivers for mysql and
postres also, so I am happy with that.  :-)

On Jan 19, 2008 12:27 PM, Briggs <acidbriggs@...> wrote:

> I'll chime in and sa NO to bundling MySQL with Netbeans.  The nice
> thing, and the reason for, Derby (JavaDB) is that it is extremely
> small, lightweight, and now part of the JDK. It gives developers the
> ability to get to work on writing applications that rely on a JDBC
> capable relational database.  This was a piece missing from the JDK.
> Most of use probably rely on a back end relational database for
> development and testing.  So, this was an extremely nice addition to
> making development easier on us.
>
> The magic of JDBC is it's extremely wonderful abstraction database
> connectivity.  What could bundling MySQL do for most people?  Not
> much.  Plus, now you have added so many extra platform dependency
> problems and extreme bloat.  Which version would you package?  With
> JavaDB we developers don't have to worry about it when just trying to
> get their development environment up and running.
>
> I would just add a plugin option that allows for the driver and
> default parameters for connecting to a mysql db.  Perhaps people could
> contribute scripts to start and stop it.  But, for me, that is about
> it. That is all you need.  Download MySQL yourself and connect to it.
> Plus, who wants the freakin' flame war of MySQL vs. Postgres vs.
> Firebird vs. whatever.
>
> I would also agree that bundling the container is a good thing.  It's
> an implementation of a a spec many of us rely on; just like JavaDB.
>
> Plus, isn't is super easy to package up a working copy of your application now?
>
> Briggs.
>

--
"Conscious decisions by conscious minds are what make reality real"

[Chuck Davis-3]

Servers ->databases->drivers

On 1/19/08, Sean Carrick <seansitsolutions@...> wrote:

> I didn't know that...where did you find them?
>
> Cheers,
>
> Sean Carrick
> PekinSOFT Systems
> PekinSOFT@...
>
> On Jan 19, 2008 5:42 PM, Briggs <acidbriggs@...> wrote:
>
> > I just realized that NB does come with the drivers for mysql and
> > postres also, so I am happy with that.  :-)
> >
> > On Jan 19, 2008 12:27 PM, Briggs <acidbriggs@...> wrote:
> > > I'll chime in and sa NO to bundling MySQL with Netbeans.  The nice
> > > thing, and the reason for, Derby (JavaDB) is that it is extremely
> > > small, lightweight, and now part of the JDK. It gives developers the
> > > ability to get to work on writing applications that rely on a JDBC
> > > capable relational database.  This was a piece missing from the JDK.
> > > Most of use probably rely on a back end relational database for
> > > development and testing.  So, this was an extremely nice addition to
> > > making development easier on us.
> > >
> > > The magic of JDBC is it's extremely wonderful abstraction database
> > > connectivity.  What could bundling MySQL do for most people?  Not
> > > much.  Plus, now you have added so many extra platform dependency
> > > problems and extreme bloat.  Which version would you package?  With
> > > JavaDB we developers don't have to worry about it when just trying to
> > > get their development environment up and running.
> > >
> > > I would just add a plugin option that allows for the driver and
> > > default parameters for connecting to a mysql db.  Perhaps people could
> > > contribute scripts to start and stop it.  But, for me, that is about
> > > it. That is all you need.  Download MySQL yourself and connect to it.
> > > Plus, who wants the freakin' flame war of MySQL vs. Postgres vs.
> > > Firebird vs. whatever.
> > >
> > > I would also agree that bundling the container is a good thing.  It's
> > > an implementation of a a spec many of us rely on; just like JavaDB.
> > >
> > > Plus, isn't is super easy to package up a working copy of your
> > application now?
> > >
> > > Briggs.
> > >
> >
> >
> >
> > --
> > "Conscious decisions by conscious minds are what make reality real"
> >
>

[Chuck Davis-3]

oops!  That should be services->databases->drivers.  Sorry.

On 1/19/08, Sean Carrick <seansitsolutions@...> wrote:

> I didn't know that...where did you find them?
>
> Cheers,
>
> Sean Carrick
> PekinSOFT Systems
> PekinSOFT@...
>
> On Jan 19, 2008 5:42 PM, Briggs <acidbriggs@...> wrote:
>
> > I just realized that NB does come with the drivers for mysql and
> > postres also, so I am happy with that.  :-)
> >
> > On Jan 19, 2008 12:27 PM, Briggs <acidbriggs@...> wrote:
> > > I'll chime in and sa NO to bundling MySQL with Netbeans.  The nice
> > > thing, and the reason for, Derby (JavaDB) is that it is extremely
> > > small, lightweight, and now part of the JDK. It gives developers the
> > > ability to get to work on writing applications that rely on a JDBC
> > > capable relational database.  This was a piece missing from the JDK.
> > > Most of use probably rely on a back end relational database for
> > > development and testing.  So, this was an extremely nice addition to
> > > making development easier on us.
> > >
> > > The magic of JDBC is it's extremely wonderful abstraction database
> > > connectivity.  What could bundling MySQL do for most people?  Not
> > > much.  Plus, now you have added so many extra platform dependency
> > > problems and extreme bloat.  Which version would you package?  With
> > > JavaDB we developers don't have to worry about it when just trying to
> > > get their development environment up and running.
> > >
> > > I would just add a plugin option that allows for the driver and
> > > default parameters for connecting to a mysql db.  Perhaps people could
> > > contribute scripts to start and stop it.  But, for me, that is about
> > > it. That is all you need.  Download MySQL yourself and connect to it.
> > > Plus, who wants the freakin' flame war of MySQL vs. Postgres vs.
> > > Firebird vs. whatever.
> > >
> > > I would also agree that bundling the container is a good thing.  It's
> > > an implementation of a a spec many of us rely on; just like JavaDB.
> > >
> > > Plus, isn't is super easy to package up a working copy of your
> > application now?
> > >
> > > Briggs.
> > >
> >
> >
> >
> > --
> > "Conscious decisions by conscious minds are what make reality real"
> >
>