Re: [GitHub] cloudstack pull request: CLOUDSTACK-8157: Add absolute schema refe...

2015-02-27 Thread Erik Weber
On Fri, Feb 27, 2015 at 10:41 AM, Nux! wrote: > Thanks for clarification, Erik. > So using custom db names should be avoided as much as possible. > > I've never tried, so I don't know how much work it would require to get working. It's certainly not impossible, but it might not be easy either :-)

Re: [GitHub] cloudstack pull request: CLOUDSTACK-8157: Add absolute schema refe...

2015-02-27 Thread Nux!
, 2015 09:22:40 > Subject: Re: [GitHub] cloudstack pull request: CLOUDSTACK-8157: Add absolute > schema refe... > On Fri, Feb 27, 2015 at 10:15 AM, Nux! wrote: > >> Hi, >> >> "Hardcoding" the name is not a very good idea, I understand that under the >&g

Re: [GitHub] cloudstack pull request: CLOUDSTACK-8157: Add absolute schema refe...

2015-02-27 Thread Erik Weber
On Fri, Feb 27, 2015 at 10:15 AM, Nux! wrote: > Hi, > > "Hardcoding" the name is not a very good idea, I understand that under the > circumstances is OK, but still. > > We have to be aware of this detail as there could be people using another > name for their DB (I did this in the past). Would up

Re: [GitHub] cloudstack pull request: CLOUDSTACK-8157: Add absolute schema refe...

2015-02-27 Thread Nux!
Hi, "Hardcoding" the name is not a very good idea, I understand that under the circumstances is OK, but still. We have to be aware of this detail as there could be people using another name for their DB (I did this in the past). Would upgrades fail for them now? This should be mentioned in the