jajwilson
commented
8 years ago That sounds reasonable to me. I think that trying to reconnect every project on the App server by hand would lead to suicidal thoughts. We need to make sure we’ve sorted every critical bug on Dev first though. I’ve got lots of meetings today, but will try to check the latest reported fixes as some point this afternoon.
James
From: thestoat [mailto:notifications@github.com] Sent: 08 October 2015 13:28 To: ox-it/ords ords@noreply.github.com Subject: [ords] ODBC retrospective data access required (#722)
With the advent of ODBC support, there is a requirement to allow the new ORDS code to access data that was created prior to the code being introduced.
Originally, ORDS used a Postgres role (typically called ords) for all data access. With the new ODBC-enabled code, ORDS now uses a different role per user to access their data. Those roles are created on data upload (if they don't already exist) and, when a user creates a database, the relevant permissions are assigned.
Obviously that will cause problems with data already uploaded, since the ORDS users and relevant permissions won't exist.
Judging by the scale of the problem I think it is better to have the permissions assigned programatically rather than by hand. There are around 150 databases on one of the app database servers (I don't have access to the other).
My questimate is 2 days effort for this.
— Reply to this email directly or view it on GitHubhttps://github.com/ox-it/ords/issues/722.
thestoat
With the advent of ODBC support, there is a requirement to allow the new ORDS code to access data that was created prior to the code being introduced.
Originally, ORDS used a Postgres role (typically called ords) for all data access. With the new ODBC-enabled code, ORDS now uses a different role per user to access their data. Those roles are created on data upload (if they don't already exist) and, when a user creates a database, the relevant permissions are assigned.
Obviously that will cause problems with data already uploaded, since the ORDS users and relevant permissions won't exist.
Judging by the scale of the problem I think it is better to have the permissions assigned programatically rather than by hand. There are around 150 databases on one of the app database servers (I don't have access to the other).
My questimate is 2 days effort for this.