Re: ConfigDepot and null values and defaults

2013-09-13 Thread Darren Shepherd
rom: Darren Shepherd [mailto:darren.s.sheph...@gmail.com] >>> Sent: Friday, September 13, 2013 1:10 AM >>> To: dev@cloudstack.apache.org; Alex Huang >>> Subject: ConfigDepot and null values and defaults >>> >>> If you have a configuration that the value i

Re: ConfigDepot and null values and defaults

2013-09-13 Thread Darren Shepherd
> >> -Original Message- >> From: Darren Shepherd [mailto:darren.s.sheph...@gmail.com] >> Sent: Friday, September 13, 2013 1:10 AM >> To: dev@cloudstack.apache.org; Alex Huang >> Subject: ConfigDepot and null values and defaults >> >> If you have

RE: ConfigDepot and null values and defaults

2013-09-13 Thread Alex Huang
> -Original Message- > From: Darren Shepherd [mailto:darren.s.sheph...@gmail.com] > Sent: Friday, September 13, 2013 1:10 AM > To: dev@cloudstack.apache.org; Alex Huang > Subject: ConfigDepot and null values and defaults > > If you have a configuration that the

ConfigDepot and null values and defaults

2013-09-13 Thread Darren Shepherd
If you have a configuration that the value is null and not dynamic, it still hits the database on every read. I'm thinking that's really not intentional. Additionally, if I have a key that is default value is 5, then I later change the default to 10. If the user never changed or set the valu