- Code that is database specfic should be in a separate file (as should be configuration code).
- Use try except blocks
- Dispose of old cursors as soon as the data is not required anymore Call Close on them.
- Keep connections open as long as required. Creating connections can be slow so it is best practice to keep them open as long as required.
- Rollback or commit frequently
- Warning.
Never, never, NEVER use Python string concatenation (+) or string parameters interpolation (%) to pass variables to a SQL query string. Not even at gunpoint. So if,
user = 'ann'
thenquery = 'select * from users where name = %s' % user
andquery = "select * from users where name = '" + user + "'"
ARE NOT GOOD - Never, never never store passwords (or password-like data) in the clear. Not even at gunpoint.
- It is an incredibly bad idea to store credit card information in a database. (unless you are a humongous company that can do it right). Always use a payment gateway/vendor.
- When you create passwords for Postgresql users (among others) always use real passwords vs. password, 12345, etc.
-
Notifications
You must be signed in to change notification settings - Fork 0
zacharski/cs350BestPractices
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
About
No description, website, or topics provided.
Resources
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published