ORM Reload throwing error

On Wed, Apr 18, 2012 at 3:31 PM, Brian Thornton <Brian@cfdeveloper.com>wrote: > I was informed that specifying ormreload for each reload when > developing is a  "no no" because this could break something if there > was not a db change... > > Any hibernate guys out there care to chime in? It's your development environment.  Who cares if you break your own environment? If you're using a shared development environment...  First, I am sorry that you hjave to work in a shared development environment.  Second, yes, running ormReload() on each and every request does have a certain amount of overhead and causes a chain reaction that digs all around the DB for datatypes, table names, columns, etc - then it might generate files, etc... It's a fairly heavy thing to do, even in development.  You probably don't want multiple people doing that on one server. they might end up stepping on each other sometimes. By yourself in a standalone development environment, it's not a big deal unless you are running concurrent requests for some reason. I usually either keep ormReload() commented out somewhere most of the time, or keep it in an if clause that looks for something like structKeyExists(url,'ormReload') to run it on demand. -Cameron -- Cameron Childress -- p:   678.637.5072 im: cameroncf facebook <http://www.facebook.com/cameroncf>; | twitter<http://twitter.com/cameronc>; | google+ <https://profiles.google.com/u/0/117829379451708140985>;