[Seaside] Postgres / Glorp / Kom

Mon May 14 18:13:16 UTC 2007

Ramiro que tal?

	I'm using WAKomEncoded39 in squeak 3.9 and it works well so far from squeak to the browser and in the contrary way. As you are also putting glorp and postgresql in the equation so I suggest to take one problem at the time. Solve persistence encoding first then, with that guaranteed use WAKomEncoded39 and see what happends. I'm not using RDBMS's right and if I use them I will probably do it in a way that utf8 will be enough because strings will end up encoded by the persistent framework. So it actually depends on the persistence framework.

	cheers,

Sebastian Sastre

> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org 
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre 
> de Ramiro Diaz Trepat
> Enviado el: Lunes, 14 de Mayo de 2007 14:55
> Para: Seaside - general discussion
> Asunto: [Seaside] Postgres / Glorp / Kom
> 
> Sorry Philippe, I am not sure what you mean.
> 
> When you say "a custom Kom" I suppose you mean extensions 
> like Norbert's.  But then, when you say "or get WideStrings". 
>  What do you mean? from where?
> 
> What happened between 3.8 and 3.9?
> Why does Kom not work with utf8 in 3.9?
> There are plenty of Spanish, German, Swedish and French 
> speakers in this list, what do you guys use in production?
> I suppose that Norbert's solution of adding hooks to 
> translate strings everytime fixes the problem, but it also 
> introduces a major performance penalty, because every string 
> that comes and goes has to get translated (everytime, unless 
> you cache the translations you make), and I guess these 
> translations are not that cheap.
> 
> 
> 
> On 5/14/07, Philippe Marschall <philippe.marschall at gmail.com> wrote:
> > No, you can either use a custom Kom or get WideStrings.
> >
> > 2007/5/14, Ramiro Diaz Trepat <ramirodt at gmail.com>:
> > > Wow...
> > > So I assume that mostly everyone not in an English 
> speaking country 
> > > with a Seaside application in production is using Squeak 3.8?
> > > Is that correct?
> > >
> > >
> > >
> > >
> > > On 5/14/07, Philippe Marschall 
> <philippe.marschall at gmail.com> wrote:
> > > > 2007/5/14, Ramiro Diaz Trepat <ramirodt at gmail.com>:
> > > > > Indeed, probably another great thing it would  be if I could 
> > > > > configure Seaside to directly send me utf8 strings from the 
> > > > > input taken on a form´s entry fields.
> > > > > Is it possible?
> > > >
> > > > Yes, this is what WAKom is doing. Just remember that 
> you also have 
> > > > to send utf8 strings to Seaside. Unfortunately WAKom 
> does not work 
> > > > on Squeak 3.9.
> > > >
> > > > Cheers
> > > > Philippe
> > > >
> > > > >
> > > > > On 5/13/07, Ramiro Diaz Trepat <ramirodt at gmail.com> wrote:
> > > > > > Hello Todd and Marcelo,
> > > > > >    I am using Squeak 3.9.
> > > > > >    I know about how to set the encoding on 
> postgres.  Indeed, 
> > > > > > utf8 is the encoding I need on the database.
> > > > > >    What I want to know is if there is any place on the 
> > > > > > Postgres, Glorp or MagritteGlorp packages where I could 
> > > > > > configure for the strings to be translated to 
> Squeak´s default (I think it´s iso).
> > > > > >    If I have, for example a Person on Glorp, and I 
> want to set 
> > > > > > a last name like mine Díaz (with an accented vowel), coming 
> > > > > > from a Magritte form for instance, on the setter I 
> translate 
> > > > > > it to UTF8 (#isoToUtf8) before I assign it to my 
> class i.var.  
> > > > > > And it gets stored on the database with no errors.  
> Later on, 
> > > > > > when Glorp "hydrates" my instance, of course it 
> brings a weird string like  "DÃ≈az", instead of "Díaz".
> > > > > >    Of course I would love that conversion to happen 
> > > > > > automatically with a little configuration.
> > > > > >    Otherwise, what are you guys doing?
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 5/13/07, marcelo Cortez 
> <jmdc_marcelo at yahoo.com.ar> wrote:
> > > > > > > Ramiro
> > > > > > >
> > > > > > >  I'm postgres user , i hope help you , postgres 
> encondig can 
> > > > > > > be configurated at database creation, postgres client can 
> > > > > > > configurated using statements SET CLIENT_ENCODING TO 
> > > > > > > 'value'; take a look at 
> > > > > > > http://www.postgresql.org/docs/8.2/static/multibyte.html
> > > > > > > best regards
> > > > > > > mdc
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --- Ramiro Diaz Trepat <ramirodt at gmail.com> escribió:
> > > > > > >
> > > > > > > > Well... sorry for building this thread by myself.
> > > > > > > > The issue now is that conversion does not happen 
> > > > > > > > automatically.  I can properly store a string on a UTF8 
> > > > > > > > database, by previously converting it using #isoToUtf8.
> > > > > > > > But when strings come back after a query (using Glorp), 
> > > > > > > > they are not converted to iso, and hence they show all 
> > > > > > > > screwed up.
> > > > > > > > Is there any place in Glorp or the Postgres driver to 
> > > > > > > > configure the encoding of the underlying database for 
> > > > > > > > these conversions to happen automatically?
> > > > > > > > Thanks !
> > > > > > > >
> > > > > > > > r.
> > > > > > > >
> > > > > > > >
> > > > > > > > On 5/13/07, Ramiro Diaz Trepat <ramirodt at gmail.com>
> > > > > > > > wrote:
> > > > > > > > > Sorry, it does work.
> > > > > > > > > I don´t know what happend.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On 5/13/07, Ramiro Diaz Trepat
> > > > > > > > <ramirodt at gmail.com> wrote:
> > > > > > > > > > I was unable to use databases with UTF8
> > > > > > > > encoding, only SQL_ASCII
> > > > > > > > > > encoding worked for me.
> > > > > > > > > > is it something trivial to configure that I did
> > > > > > > > not see or is it a limitation?
> > > > > > > > > > Thanks
> > > > > > > > > >
> > > > > > > > > > r.
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > __________________________________________________
> > > > > > > Preguntá. Respondé. Descubrí.
> > > > > > > Todo lo que querías saber, y lo que ni 
> imaginabas, está en 
> > > > > > > Yahoo! Respuestas (Beta).
> > > > > > > ¡Probalo ya!
> > > > > > > http://www.yahoo.com.ar/respuestas
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> 