On Tuesday 26 February 2002 14:47, Daisuke Maki wrote: > > How are you doing your queries? I'm sure we could find a better way. ESQL > > has in built support for alternate encodings in the database, for example > > (or at least it should, assuming I wrote that part already...). > > I have a DBI wrapper which proxies most requests to DBI, but sometimes > does some additional tasks... I kind of need these, so while I'm no ESQL > expert, that probably won't flow too well... probably. > > I suppose I could > > - force the queries to return UTF-8 by converting them dynamically, or > - force the inputs to the database to UTF-8 when users submit them. > > And if I can just forget about the EUC-JP bit, everything is peachy. Ah > well, I guess I understand how you guys feel. This problem sucks :)
>From an application architectural point of view I have to agree with Daisuke. ESQL tag lib is a fine thing, but I build large scale applications that make heavy use of databases. I cannot recall the last time I wrote one that wasn't built around a wrapper/abstraction layer on top of DBI. In any decently complex application I just don't see XSP as the place to be interfaceing to your database. It presupposes that ONLY web pages will use the database, or else you have to carefully replicate logic in other perl code. So at that point you are better off writing a wrapper (which isn't tied to XSP) and building a custom taglib. I think where ESQL taglib IS really usefull is in building generalized web based database interfaces, like admin and debugging tools, or perhaps other similar situations. > > --d > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
