On Tue, Aug 13, 2019 at 9:02 PM Nicolas Couchoud < nicolas.couchoud__ledgersmb@normalesup.org> wrote:
Erik Huelsmann a écrit :
I've created a change to the code base which is at least a step in the right direction. Could you check that it works when you place these files on your server:
https://github.com/ledgersmb/LedgerSMB/blob/ 8f5782ee9fe2e6159f42b652fd77c331dd25a737/lib/LedgerSMB/PGOld.pm https://github.com/ledgersmb/LedgerSMB/blob/ 8f5782ee9fe2e6159f42b652fd77c331dd25a737/lib/LedgerSMB/PGObject.pm
?
Hi,
It seems to work, thank you !
Great! Thanks for the confirmation. I can make the suggested adjustments and merge the branch to make a new release.
I found other places where schema public explicitely appears : * In sql/changes/1.5/open_forms_callers.sql, there are three requests explicitely mentioning table « public.open_forms ». This prevents the complete upgrade of the tables from 1.3 to 1.5. I patched the file by suppressing « public. » and it works.
Hmm. Ok. In order to prevent future updates from going breaking on your database, I need a bit of information from you: In your database, there's a table called "db_patches". This table has a 'sha' and a 'path' column. I need the content of the 'sha' column for each of the files you patched (indicated in the 'path' column). Could you send me the sha of that file? I want to see if I can recreate the same SHA. (or that I need to send you a new sha for that column...)
* In sql/modules/Roles.sql, there is a request « GRANT ALL ON SCHEMA public TO public; ».
I'll update that one too. Thanks again! Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.