Skip to content
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

Connection logging scripts should be two separate files (W) #14

Closed
wildtayne opened this issue Jun 14, 2017 · 2 comments
Closed

Connection logging scripts should be two separate files (W) #14

wildtayne opened this issue Jun 14, 2017 · 2 comments
Assignees
Labels
Milestone

Comments

@wildtayne
Copy link
Contributor

Connection logging setup has two parts - One time setting of server configuration, and creation of logging functions. These should be split into their own SQL files.

@wildtayne wildtayne self-assigned this Jun 14, 2017
@wildtayne
Copy link
Contributor Author

I've relocated all of the logging setup (statements that need to be run only once), including the ddl triggers, into prepareUserLogging.sql. We can discuss if we want to break the ALTER SYSTEM statements into a separate file.

@wildtayne
Copy link
Contributor Author

I propose that the logging setup all be kept in the current file. We may also want to remove the log columns from classdb.student and add them as ALTER statements to prepareUserLogging.sql. This would make the logging system self-contained and optional.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant