Good idea Daan!
Regards. ________________________________ From: Daan Hoogland <daan.hoogl...@gmail.com> Sent: Friday, July 12, 2024 17:09 To: dev <dev@cloudstack.apache.org> Cc: us...@cloudstack.apache.org <us...@cloudstack.apache.org> Subject: stored procedures and versions (Was: [VOTE] Apache CloudStack 4.19.1.0 (RC1)) This is a bit off topic, so renaming the thread. Can we instate a similar procedure as for views for stored procedures? it seems to me we can de exactly the same for those stored procedures and maybe even hijack the views dir so no issues occur with those in the future. It would guarantee these are recreated on every update and also always have the latest version as needed. On Fri, Jul 12, 2024 at 11:37 AM Suresh Kumar Anaparti <sureshanapa...@apache.org> wrote: ... > > ________________________________ > > From: Nux <n...@li.nux.ro> > > Sent: Friday, July 12, 2024 02:44 > > To: dev@cloudstack.apache.org <dev@cloudstack.apache.org> > > Cc: users <us...@cloudstack.apache.org> > > Subject: Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1) > > > > Rohit, > > > > That's a very good point about the routines, thanks for sharing how to > > restore them. ... > > On 2024-07-11 12:52, Rohit Yadav wrote: ... > > > * > > > I hit an issue with idempotent routines missing on cloud_usage db > > > (borrowed them from mbx env with: mysqldump --no-create-db > > > --no-create-info --no-data --routines cloud_usage > > > > cloud_usage-routines.sql ; and applied this in my homelab env; likely > > > my fault while moving DB servers and forgot the -R option where I > > > forgot to backup the routines) -- Daan
