I don't think there's some kind of convention on how to use Sequel with a Rails application so it's unlikely you'll find any generic way to apply to your gem. Maybe you could check for the existence of Sequel::Model.db or the constant DB. Other than that I don't think there's much more you could do... Maybe searching for an instance of Sequel::Database in the existent objects...
Having said that, I believe people should really call Sequel::Model.db= in any application making use of Sequel Models. Just add a note in the README asking users to do so if they don't do it already. We do it for our Rails app. Also the DB constant is also defined for us. Hope it helps, Rodrigo. Em domingo, 10 de novembro de 2013 19h54min12s UTC-2, Kenny Meyer escreveu: > > I am building a gem to annotate Sequel models in Rails projects: > https://github.com/kennym/annotate-sequel > > It is not working yet, because whenever I require a Rails model to parse > its schema information I am getting the following error: > > No database associated with Sequel::Model: have you called > Sequel.connect or Sequel::Model.db= > > I do understand what the error is about, but I would like to gather your > feedback on how you could get the Rails connection details from within the > gem, without supplying that information separately. > > Looking forward to read your answers! > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/groups/opt_out.
