Project

General

Profile

Bug #3618

Auth Dbo: Consider adding schema support for UserDatabase

Added by Bruce Toll about 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
10/02/2014
Due date:
% Done:

0%

Estimated time:

Description

Wt Dbo provides good support for schema-qualified tables and it might be helpful in some use cases to place Auth Dbo tables in a separate schema.

However, the current Wt github (3.3.3-19-gad17d0b) does not quote all schema references and this results in "relation ... does not exist" errors with Postgresql.

The first attached patch adds support for schema qualified tables. It has been lightly tested with Postgres. The patch has a dependency on the tableNameQuoted method provided in patch with issue #3616, and serves as a sample use case. As a note, the auth_token table will include a column name of the form "user_schema.auth_info_id". This works, as it is quoted by Dbo and is a valid Postgres column name, but it might be unexpected.

A second attached patch provides some rudimentary database tests of Auth Dbo, both with and without schemas.


Files

#1

Updated by Bruce Toll about 8 years ago

Please note that the second patch (test code) was only built and tested with Postgres and Sqlite. Sqlite does not support schema-qualified tables, so the schema test is only done for Postgres at this time.

#2

Updated by Koen Deforche about 8 years ago

  • Status changed from New to InProgress
  • Assignee set to Wim Dumon
  • Target version set to 3.3.4
#3

Updated by Koen Deforche about 8 years ago

  • Assignee changed from Wim Dumon to Koen Deforche
#4

Updated by Koen Deforche about 8 years ago

  • Status changed from InProgress to Resolved

Hey Bruce,

Good idea, thanks.

Koen

#5

Updated by Koen Deforche about 8 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF