I'm not sure why update would be having this issue. I thought I've used it without problems. It should only update the tables if they domain objects have changed.
-Scott On Thu, Feb 21, 2008 at 3:46 PM, Sudirikku Mohanjith <[EMAIL PROTECTED]> wrote: > Hi Mike, > Everything is fine, if I remove the property. > > I'll update the wiki. I think it should be <prop > key="hibernate.hbm2ddl.auto">create</prop> at the initial deployment, > i.e. you want to create the tables. > Then the property should be removed. > > Scott, can you confirm whether that's the way it should be? > > Cheers, > Mohanjith > > On Fri, Feb 22, 2008 at 2:05 AM, Mike Kennedy <[EMAIL PROTECTED]> wrote: > > Ah sorry, I read your initial email wrong. That's what I get for > skipping > > lunch I suppose. > > > > What happens if you remove that property altogether? > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On > > Behalf Of Sudirikku Mohanjith > > > > Sent: Thursday, February 21, 2008 12:19 PM > > To: Yale CAS mailing list > > > > > > Subject: Re: CAS services registry status > > > > Hi Mike, > > Thanks for the quick reply, > > > > In my case hibernate.hbm2ddl.auto is set to update, > > > > <prop key="hibernate.hbm2ddl.auto">update</prop> > > > > Also if it was set to create-drop, none of the records will persist, > > but it's only the statuses that doesn't persist. > > > > My gut feeling is it is something to do with BIT datatype that is used > > for boolean fields. > > > > Cheers, > > Mohanjith > > > > On Fri, Feb 22, 2008 at 1:27 AM, Mike Kennedy <[EMAIL PROTECTED]> wrote: > > > Mohanjith, > > > > > > I think its because you probably have this property set in the > > > entityManagerFactory bean: > > > > > > <prop key="hibernate.hbm2ddl.auto">create-drop</prop> > > > > > > I think if you remove this line once the database is created you > should > > be > > > ok. > > > > > > Mike > > > > > > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] On > > > Behalf Of Sudirikku Mohanjith > > > Sent: Thursday, February 21, 2008 11:35 AM > > > To: Yale CAS mailing list > > > Subject: CAS services registry status > > > > > > Hi, > > > In my CAS deployment I'm using ServiceRegistry DAO based on MySQL > and > > > Hibernate, as explained in > > > http://www.ja-sig.org/wiki/display/CASUM/Configuring. However the > > > status of the services in the registry is always reset everytime I > > > restart the application server. > > > > > > Any help will be appreciated. > > > > > > Cheers, > > > Mohanjith > > > _______________________________________________ > > > Yale CAS mailing list > > > [email protected] > > > http://tp.its.yale.edu/mailman/listinfo/cas > > > > > > _______________________________________________ > > > Yale CAS mailing list > > > [email protected] > > > http://tp.its.yale.edu/mailman/listinfo/cas > > > > > _______________________________________________ > > Yale CAS mailing list > > [email protected] > > http://tp.its.yale.edu/mailman/listinfo/cas > > > > _______________________________________________ > > Yale CAS mailing list > > [email protected] > > http://tp.its.yale.edu/mailman/listinfo/cas > > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > -- -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
