We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
#2 will allow for custom and varied interfaces. Postgres has notify/listen, as well as atomic operations, which makes it great for this.
The only problem is expiration of keys, which isn't a huge deal. It could be handled with a trigger (see http://stackoverflow.com/questions/26046816/is-there-a-way-to-set-an-expiry-time-after-wich-a-data-entry-is-automatically), or document and expect the user to manually clean old responses with whatever scheduling system they prefer. Expose a nice python-side method to clear the table as well.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
#2 will allow for custom and varied interfaces. Postgres has notify/listen, as well as atomic operations, which makes it great for this.
The only problem is expiration of keys, which isn't a huge deal. It could be handled with a trigger (see http://stackoverflow.com/questions/26046816/is-there-a-way-to-set-an-expiry-time-after-wich-a-data-entry-is-automatically), or document and expect the user to manually clean old responses with whatever scheduling system they prefer. Expose a nice python-side method to clear the table as well.
The text was updated successfully, but these errors were encountered: