Closed thbar closed 12 years ago
Some DDL statements blow up with schema prefix, obviously. I tend to use a rails initializer for ActiveRecord and extend the Migration class with this helper that I sometimes use in migrations.
https://gist.github.com/1861074
Hi Ken - thanks! Good to know. Can I add a note on the README about that maybe to point to this?
(In this case I will just ensure I stick with the dbo schema).
Sure!
On Feb 18, 2012, at 4:44 PM, Thibaut Barrère wrote:
Hi Ken - thanks! Good to know. Can I add a note on the README about that maybe to point to this?
(In this case I will just ensure I stick with the dbo schema).
Reply to this email directly or view it on GitHub: https://github.com/rails-sqlserver/activerecord-sqlserver-adapter/issues/165#issuecomment-4037579
Wont fix, documentation issue with possible later pull request.
(I'm just discovering the adapter so please bear with me!)
I have a user whose default schema is not dbo. I tried to use this to work-around it (as recommended on the readme):
but this leads to:
I was able to work around that with by changing the default schema on the user (but that's not always doable):
Is the
table_name_prefix
trick supposed to handle what I supposed it was?