Hi guys. It may happen that both, Glorp and the database driver in
question, support an encoding strategy. In Pharo, both drivers
(NativePostgresDriver and OpenDBXDriver) does support setting an encoding
and take care of it. But Glorp supports that as well.
I want to avoid doing double
On 10 Jul 2013, at 17:00, Mariano Martinez Peck marianop...@gmail.com wrote:
Hi guys. It may happen that both, Glorp and the database driver in question,
support an encoding strategy. In Pharo, both drivers (NativePostgresDriver
and OpenDBXDriver) does support setting an encoding and take
2013/7/10 Sven Van Caekenberghe s...@stfx.eu:
So...where should I do the conversion? At Glorp level or at database driver
level?
And IMHO at the lowest possible level. If you have an SQL VARCHAR column, the
driver should convert bytes to a normal Smalltalk String. An OR mapper is a
client
