I''m looking for a better way of storing user options (what stylesheet to use, and stuff like that) for my rails app. The data I need to store is very simple and there will only ever be one options instance per user and there will probably never be more than one user. I feel that putting up an ActiveRecord model for this would be overkill. But on the other hand I wan''t something that will survive sessions. What''s the middle ground in Rails persistence? -- Alex Polite
Seemingly Similar Threads
- Pinouts for T1/E1 crossover cable WAS "RE: what cable to connect a legacy PBX to a TE410P ?"
- Extending instance-methods of an Module for Plugin-Development
- VPN Single Daemon For LAN/WAN
- VPN Single Daemon For LAN/WAN
- IPSEC, multiple subnets and multiple road warriors, oh my! :)