Yuval Kordov comments

Results 13 comments of


Yuval Kordov

422 Unprocessable Entity on save

Are you possibly using a virtual hosted style URL for your bucket? I.e. `bucketname.s3.amazonaws.com` rather than a path style URL `s3.amazonaws.com/bucketname`?

AR is erroneously validating existing records on a has_many :through

I haven't no. I just confirmed this is still an issue in 4.2.

AR is erroneously validating existing records on a has_many :through

@tenderlove From 3.2.18 :( No going back to that one! I also can't guarantee that it wasn't happening in Rails 3, only that I hadn't recalled seeing it before.

AR is erroneously validating existing records on a has_many :through

So its a 5 year old problem... :)

AR is erroneously validating existing records on a has_many :through

Bless your heart.

AR is erroneously validating existing records on a has_many :through

Giant hugs all around.

ActiveRecord::StatementInvalid: PG::Error: ERROR: relation "pg_search_documents" does not exist

I tried doing the same thing with my Comment model and didn't encounter any issues, which leads me to believe there's a reserved term issue with models named "Document" and...

ActiveRecord::StatementInvalid: PG::Error: ERROR: relation "pg_search_documents" does not exist

Finally had time to open up the lib and there it is, Document as an un-namespaced class. Would there be any chance of either namespacing this under PgSearch or renaming...

ActiveRecord::StatementInvalid: PG::Error: ERROR: relation "pg_search_documents" does not exist

It is name spaced, but as soon as you include PgSearch the name spacing is rendered moot. I've submitted pull request 96 that renames the class to something less generic,...

ActiveRecord::StatementInvalid: PG::Error: ERROR: relation "pg_search_documents" does not exist

You're right, but that is a more specific, less likely scenario, especially in an environment where pg_search is being used. We could go as far as naming it PGSearchDocument to...