If your app is about searching (business directories, dictionaries, etc) or a catalog of browsable items, it’s always a good idea to let your API use a read-only database user. Another use case would be for doing backups, no write permissions needed either.
Here is how to do that for PostgreSQL v9.0+ (syntax quasi-similar for MySQL):
-- Say we just created the user "pouet"
-- Allow the user to CONNECT
GRANT CONNECT ON DATABASE mydb TO pouet;
By: @BTroncone
Also check out my lesson @ngrx/store in 10 minutes on egghead.io!
Update: Non-middleware examples have been updated to ngrx/store v2. More coming soon!
Table of Contents
| internal static class FormsAuthenticationTicketHelper | |
| { | |
| private const byte CURRENT_TICKET_SERIALIZED_VERSION = 0x01; | |
| private const int MAX_TICKET_LENGTH = 4096; | |
| // Resurrects a FormsAuthenticationTicket from its serialized blob representation. | |
| // The input blob must be unsigned and unencrypted. This function returns null if | |
| // the serialized ticket format is invalid. The caller must also verify that the | |
| // ticket is still valid, as this method doesn't check expiration. |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
