RE: Re: [Hibernate] automatic db creation

[ROSSEL Olivier <ol...@airbus.com>]

Once again a central point for references to database libraries would
greatly 
improve the productivity of developpers.

May be at db.apache.org there could be a link called "resources"
that would link to other interesting pieces of software.



> -----Message d'origine-----
> De: travis@spaceprogram.com [mailto:travis@spaceprogram.com]
> Date: lundi 24 mars 2003 22:51
> À: Aaron Metzger; hibernate-devel@lists.sourceforge.net
> Objet: RE: Re: [Hibernate] automatic db creation
> 
> 
> Hi all,
> 
> Just got back from vacation and glad to hear that this 
> discussion has been sparked up again.  Aaron has pointed out 
> the best reason for having this feature, ie: deploying 
> changes to multiple clients.  Others include, ease of 
> development and initial deployment.
> 
> Anyways, as for being smart with updates, we did this in OJB 
> at apache by adding new columns if they don't exist and we 
> are using crossdb to do the table creation and altering.  
> www.crossdb.com  This ensures that the same code can modify 
> various databases seamlessly.
> 
> So in creating this feature, I would propose using crossdb 
> for it as it will work and make the feature quite easy to create.
> 
> Travis
> 
> ---- Original Message ----
> From: Aaron Metzger <am...@silkspeed.com>
> Sent: 2003-03-18
> To: hibernate-devel@lists.sourceforge.net
> Subject: Re: [Hibernate] automatic db creation
> 
> > 
> > 
> > Yes - and that is that such an "reliable runtime update" 
> really has to be
> > smart :)
> > And I would like to hear how reliable such a tool can be ?
> > It seems as an almost unsolvable problem to me :)
> > 
> > /max
> > 
> > 
> 
> 
> Your correct that it is a tough problem given the lack of 
> features and 
> standardization across the database engines with respect to 
> "alter table".
> 
> However, the 90% use case is "add a new table" or "add a new column" 
> which most vendors do support.  So, a first cut for the smart-update 
> is that it solves the problem or is smart enough to know that 
> it can't 
> solve the problem and tells you that it can't.
> 
> In the role of pushing out production code to customers, I will know 
> if the upgrade is one that can be handled by smart-update or not.  If 
> it can, I just give them new code without having to give them a 
> separate database update script, procedures for running it, and the 
> involvement of their expensive DB admin.  I have a solution like this 
> in my own home-grown BMP persistence engine which has allowed me to 
> just send new ".ear" files to my customers for years without them 
> having to know that a database schema change occurred.  I'm hoping to 
> be able to use Hibernate just as transparently.
> 
> The post regarding the Eclipse Plugin is great news for 
> developers but 
> doesn't help the end customer that is receiving a bundle of software 
> that they need to install.  Maybe I have the odd case here because I 
> ship applications which end-users install and manage.  My developers 
> are not the ones doing production installation.
> 
> 
> 
> -- 
> Aaron Metzger
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Does your code think in ink? 
> You could win a Tablet PC. Get a free Tablet PC hat just for playing. 
> What are you waiting for?
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> _______________________________________________
> hibernate-devel mailing list
> hibernate-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> hibernate-devel mailing list
> hibernate-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel
> 
> This mail has originated outside your organization,
> either from an external partner or the Global Internet. 
> Keep this in mind if you answer this message.
>