Custom table name

[ambentzen]

Use table name from SqlSession
Added tests to custom table name

Don't use Rails 4.0.0

Added upper bound on rails dependencies

Usage

Set SmartSession::SqlSession.table_name to your desired name in the config somewhere appropriate (such as config/application.rb). And remember to update/create the session migration.

[fcheung]

Cool. Out of interest, what breaks in rails 4?

[ambentzen]

Probably nothing, but I have not tested against it. And I might have gone a bit overboard with the commit squashing.

It should not be hard to make a travis scheme to test against both 3.x and 4.0. I'm going to do that right now.

[ambentzen]

On Rails 4.0.0 there are 9 failures and 2 errors, and a lot of deprecation warnings.

[fcheung]

Thanks for checking. The only comment I have really is that I don't think those specs check that the customs table name is actually being used? Running the whole test suite again seems a little over the top and like I said doesn't I think achieve anything in the current state. I think if the tests set the table name to something custom and only created that custom name then I think we could be confidant that there isn't a hard coded 'sessions' hanging around somewhere.

[ambentzen]

You are completely correct, I will look into that tomorrow. The proper way to do it is probably to create a 'sessions' schema and a 'sessions_custom' schema and make sure they are used in the proper context.