Fix #27 by casting literal strings to varchar in projection lists only#36
Conversation
rwasef1830
changed the title
|
@Emill, will you have time to look into this? There's also npgsql/npgsql#1045 which was wrongly closed (branch rename). Hopefully we can finally put this issue to rest at some point... |
|
I would like to note that the approach in this pull request is far less breaking than the other one. |
rwasef1830
force-pushed
the
bug_27_literal_varchar_in_projection_lists_only
branch
from
0925f9c to
a2563ae
Compare
|
Sorry this hasn't received much attention, I've been busy with the 3.1 release and other stuff... Promise to dive in soon. |
rwasef1830
force-pushed
the
bug_27_literal_varchar_in_projection_lists_only
branch
from
a2563ae to
a2c7229
Compare
|
Squashed to a single commit for easy fast-forward merge and review ;-) |
|
@rwasef1830, just to let you know I haven't forgotten about this (even though it's been a month). I'm really taken up with other things but promise to find some time soon... |
rwasef1830
force-pushed
the
bug_27_literal_varchar_in_projection_lists_only
branch
from
a2c7229 to
a0d32ac
Compare
…it cast function + tests.
rwasef1830
force-pushed
the
bug_27_literal_varchar_in_projection_lists_only
branch
from
a0d32ac to
e1689b9
Compare
|
Updated to fix conflicts and be ready for review and merge (wink) in next fix release. |
2 participants
This fixes bug #27 with a tiny behavioral change that would only rarely affect unlikely query scenarios. And in that case a workaround is possible by just using an explicit cast.