Andy - my opinion would be to use a database table. Why would this be
too much? The user settings sounds like something that needs to be
persisted, and the db is the ideal place for storing persistent data,
maybe even the only sensible place. Also, Rails makes it easy to get
stuff in and out of the db so it isn’t much programming effort.
Well, it’s because there are only a few things that the user could
change, so i thought database is a bit too much.
If i use a database, what would be the best approach to store different
settings? Do i use store a single value in each row e.g. a row to store
the status value, another row to store the default admin’s email, etc?
Or do i store them as a single row under different fields?
One more thing, I’m using the example from the Agile Web D. in
Rails to handle uncaught exception. In my application controller i
declared a method called
The thing is, the exception doesn’t get caught. The exception gets
caught if i change the method to
Any idea why?