On 10 Jul 2013, at 17:00, Mariano Martinez Peck <[email protected]> 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 care of it. But > Glorp supports that as well. > I want to avoid doing double conversion... > > So...where should I do the conversion? At Glorp level or at database driver > level? > Is glorp trustful enough for the encoding? UserGuide says nothing about it. It should certainly only happen once ! 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 of the driver, right ? > Thanks, > > -- > Mariano > http://marianopeck.wordpress.com
