-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NEW : payment on several expense report (SQL integration) #24884
base: develop
Are you sure you want to change the base?
NEW : payment on several expense report (SQL integration) #24884
Conversation
…nt_on_several_expense_report_sql
…nt_on_several_expense_report_sql
…nt_on_several_expense_report_sql
…nt_on_several_expense_report_sql
…nt_on_several_expense_report_sql
…nt_on_several_expense_report_sql
@@ -16,14 +17,14 @@ | |||
-- | |||
-- =================================================================== | |||
|
|||
create table llx_payment_expensereport | |||
create table llx_paymentuser |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suppose goal of renaming is to avoid confusion with the new intermediate table llx_payment_expense_report
This may have larger impact than just adding the new table.
So to make transition easier, i suggest to just use the name for the intermediate table (the one you called "llx_payment_expense_report"):
llx_expensereport_payment_expensereport
(meaning link between "expensereport" and "payment_expensereport")
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the following PR of this one : #23702