Re: [DISCUSSION] Management of the database's "VIEW"s

2023-04-07 Thread Daniel Salvador
Hello guys, Sorry for the delay; I created PR 7417 [¹] to address the discussion we had in this thread. Best regards, Daniel Salvador (gutoveronezi) [¹] https://github.com/apache/cloudstack/pull/7417 On Tue, Feb 14, 2023 at 10:37 AM Wei ZHOU wrote: > Agree with Daan. go for it @Daniel > > O

Re: [DISCUSSION] Management of the database's "VIEW"s

2023-02-14 Thread Wei ZHOU
Agree with Daan. go for it @Daniel One problem that needs to be solved is, there are few SQL upgrade scripts that rely on views. You can check by command git grep "_view" engine/schema/src/main/ |egrep -v -i 'DROP VIEW|CREATE VIEW' Kind regards, Wei On Tue, 14 Feb 2023 at 14:27, Daan Hoo

Re: [DISCUSSION] Management of the database's "VIEW"s

2023-02-14 Thread Daan Hoogland
Daniel, I think this is a lazy consensus issue and any further discussion can happen on a PR. No vote thread needed. On Mon, Feb 13, 2023 at 10:45 PM Daniel Salvador wrote: > I think I messed up with the format of my last email. Here follows the > message in the correct format: > > --- > > Thank

Re: [DISCUSSION] Management of the database's "VIEW"s

2023-02-13 Thread Daniel Salvador
I think I messed up with the format of my last email. Here follows the message in the correct format: --- Thank you for the replies, guys. I agree using frameworks (ORM and/or OOQ) might facilitate CloudStack's developers' life. Given the complexity of the project and the whole analysis and disc

Re: [DISCUSSION] Management of the database's "VIEW"s

2023-02-13 Thread Daniel Salvador
> > Thank you for the replies, guys. > > I agree using frameworks (ORM and/or OOQ) might facilitate CloudStack's > developers' life. Given the complexity of the project and the whole > analysis and discussion necessary, it would require a lot of effort and > time to implement it, as Daan mentioned;

Re: [DISCUSSION] Management of the database's "VIEW"s

2023-02-08 Thread Daan Hoogland
great. > > > > [1] > > > https://www.jooq.org/doc/latest/manual/sql-building/ddl-statements/create-statement/create-view-statement/ > > [2] https://flywaydb.org/ > > > > > > Regards. > > > > > > From: Daan Hoogland > > Sent: Tuesday, Febru

Re: [DISCUSSION] Management of the database's "VIEW"s

2023-02-08 Thread Wei ZHOU
create-view-statement/ > [2] https://flywaydb.org/ > > > Regards. > > > From: Daan Hoogland > Sent: Tuesday, February 7, 2023 19:12 > To: dev@cloudstack.apache.org > Subject: Re: [DISCUSSION] Management of the database's "VI

Re: [DISCUSSION] Management of the database's "VIEW"s

2023-02-07 Thread Rohit Yadav
d? I would think we > can > > remove the file from the views directory and add the drop view SQL on the > > schema file. > > > > Regards, > > Nicolas Vazquez > > > > From: Daniel Augusto Veronezi Salvador > > Sen

Re: [DISCUSSION] Management of the database's "VIEW"s

2023-02-07 Thread Daan Hoogland
remove the file from the views directory and add the drop view SQL on the > > schema file. > > > > Regards, > > Nicolas Vazquez > > > > From: Daniel Augusto Veronezi Salvador > > Sent: Monday, February 6, 2023 9:43 PM >

Re: [DISCUSSION] Management of the database's "VIEW"s

2023-02-07 Thread Daniel Salvador
or > Sent: Monday, February 6, 2023 9:43 PM > To: dev@cloudstack.apache.org > Subject: [DISCUSSION] Management of the database's "VIEW"s > > Hello guys, > > I would like to open a discussion on our current management of the > database's "VIEW&

Re: [DISCUSSION] Management of the database's "VIEW"s

2023-02-07 Thread Nicolas Vazquez
Veronezi Salvador Sent: Monday, February 6, 2023 9:43 PM To: dev@cloudstack.apache.org Subject: [DISCUSSION] Management of the database's "VIEW"s Hello guys, I would like to open a discussion on our current management of the database's "VIEW"s. Currently, we have

[DISCUSSION] Management of the database's "VIEW"s

2023-02-06 Thread Daniel Augusto Veronezi Salvador
Hello guys, I would like to open a discussion on our current management of the database's "VIEW"s. Currently, we have to look at the changes in the previous "schema" files and replicate the whole "CREATE VIEW" command in the current "schema" file, modifying what we need (adding/removing column