-
Notifications
You must be signed in to change notification settings - Fork 31
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
Release #25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix sql_firewall_import_rule() to check file status before importing a rule file. #2
Previously, JumbleRangeTable() used relation oid on query jumbling, and it resulted different queryid when relid gets changed. Now, JumbleRangeTable() uses relation name instead of relid to calculate queryid, so queryid could be the same when table gets dropped and created with the same name.
Fix JumbleRangeTable() to jumble query with relation name. #13
Fix to suppress `unused-const-variable' warning. #6 Eliminate unused code to suppress `unused-const-variable' warning caught on OS X.
FIX small typo, missing char
Add copyright notice.
Fix copyright notice.
…e oid. To keep the same queryid after re-creating (user) functions, JumbleExpr() has to use function name instead of the oid. Although JumbleExpr() still depends on several oids of other type of database objects, such as window functions or aggregation functions, using user function name and table name seems to be good enough so far. See /* FIXME */ comments for those objects which still use oid.
Fix JumbleExpr() to use function name on query jumbling instead of the oid.
JumbleQuery() is exposed to other modules to calculate QueryId, and to keep it the same value in the different extensions.
Fix JumbleQuery() to be exposed to other extensions.
Compatibility about major versions and rule files explained.
Fix README to add new compatibility section.
Add ChangeLog.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SQL Firewall 0.8.1.