-
Notifications
You must be signed in to change notification settings - Fork 348
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
implement postgres naming strategy; fixes #215 #218
Conversation
@fwbrasil @gustavoamigo @lvicentesanchez @jilen please review. p.s. I've noticed builds in last couple of PRs have been failing on MySQLAsync/PostgresAsync. Rebuild passes though, not sure if temporary or something to look into. |
@@ -80,11 +80,15 @@ trait CamelCase extends NamingStrategy { | |||
} | |||
object CamelCase extends CamelCase | |||
|
|||
trait PostgresEscape extends Escape { | |||
override def column(s: String) = if (s.startsWith("$")) s else default(s) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not else super.column(s)
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
never mind, clean build solved AbstractMethodError
I was getting, will update PR.
I'll grab stack trace if spurious build error occurs again.
implement postgres naming strategy; fixes #215
@godenji Thanks for the quick fix! :) |
@fwbrasil speaking of quick fixes there's actually a bunch of cleanup work to do (various typos in source files and readme phrasing/grammar) before you give your ScalaDays talk in Berlin 😄 I'll try to make note of them as they come up, get distracted by the interesting work and then forget the little details... |
@godenji awesome! looking forward to it! |
@godenji I've just noticed that this change wasn't reflect in the readme, could you fix it? |
No description provided.