From: Milan B. <mil...@gm...> - 2008-06-18 21:32:41
|
On 6/18/08, Kjell Rilbe <kje...@da...> wrote: > Now, I try to connect with FR set to use charset NONE. Connecting with NONE is a bad idea, you should only do it when you don't want FB and FR to do any transliteration. This would only work correctly when you have ASCII-only characters or your environment charset matches the database charset (for example, having UTF8 database on Linux). > By copying identifier names I come up with this SQL: > > alter table "Användare" > add constraint "AnvändareLösenordLängd" > check (char_length("Lösenord") >= 8); > > Executes fine and now commit works too. As expected. No transliteration in any direction = no mangling. > Disconnect and reset to use ISO8859_1. Now everything looks nice again! > Even when viewing the constraints in table properties sheet - no mangled > identifiers. I also can confirm that the check works. > > So, who's doing something wrong with the identifiers here? FB or FR? > > Does FB store identifiers in UTF8 or in the db:s default charset? I don't know. I also don't know whether identifiers are transliterated by FB (as data is), and I believe there were some changes introduced by 2.1 in this area. Also, IIRC, there are still changes to be seen in FB 2.5 about all this. I guess I'll have to investigate this deeper before giving any definite answer. My guess is that everything works fine with FB 2.0 ? -- Milan Babuskov http://www.flamerobin.org |