On Mar 21, 2:09 pm, dave lilley <[email protected]> wrote: > Thanks rohit, > > I had looked through github, my rdocs from the gem but didn't think of > looking at the rubyforge site!! > > tonight when i get home I shall test this out. > Also tried searching for example usage of stored procedures within sequel > github and my gem structure with no luck not to mention googling. > > Question - Is what I am trying to do something not normally done?
Well, not that many people using Sequel use stored procedures. But it was added for a reason, and it is tested on MySQL at least, both with the mysql and jdbc adapters. I've heard it works elsewhere, except that IN/OUT parameters aren't necessarily handled. > if this is the case what would be considered mainstream? > also is there any examples of usage for the full_text_search? If your dataset supports it (e.g. for MSSQL, Postgres, and MySQL): DB[:table].full_text_search([:column1, :column2], ['term1', 'term2']) > I refer to this url -http://sequel.rubyforge.org/rdoc-adapters/index.html > I am only too happy to do something as a worked example and post to this > forum or github. More examples would certainly help. Full text search using Sequel certainly isn't explained in detail anywhere, and I'd be happy to include more documentation about it. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
