Options for CGI::Session database_manager objects?

ruby-talk
1

I’m looking at the source for pgsession at the moment, and it appears
that he simply puts things like the hostname, port, db_user, etc as
hardcoded strings in his class definition.

I thought that was odd, so I looked over the CGI::Session
documentation, and I can see why he did that. Is there no faculty to
pass options to your database_manager when using CGI::Session?

What have people done in the past? Something like this maybe?

CGI::Session::MyDatabaseManager.set_options(aHash)

(That’s what I’m going to end up doing, as it were.)

2

Samuel Tesla samuel@alieniloquent.com writes:

I thought that was odd, so I looked over the CGI::Session
documentation, and I can see why he did that. Is there no faculty to
pass options to your database_manager when using CGI::Session?

It’s (sort of) undocumented, but it appears that CGI::Session passes
the entire options hash into the database_manager object. I should
just glance at the code more often! :stuck_out_tongue: