>From my experience with it, firebird requires you to specify the collation during the creation of a table. I don't know if the latest versions have a default setting. In the past, not only one had to specify it during creation, it was also very difficult changing it aftewards.
Regarding orderby='table.field collate de_de', does this work with all databases? I would have thought that icu would be needed for this to work with sqlite? On Jan 14, 3:46 pm, mdipierro <[email protected]> wrote: > about collate. > > My understanding is that collate in table definition is not required. > In web2py you can specify it upon sorting with: > > orderby='table.field collate de_de' > > Massimo > > On Jan 14, 9:29 am, mdipierro <[email protected]> wrote: > > > I have not done the tests on firebird myself but my understanding was > > that by calling the following SQL > > > SET NAMES UTF8; > > > it is no longer necessary to specify a collate for every column. Is > > this wrong? > > On your system this produces an error. Why is that? Can you issue the > > statement to firebird manually outside web2py? > > > Massimo > > > On Jan 14, 7:06 am, Petros Diveris <[email protected]> wrote: > > > > I am not sure as to why you are getting this. Btw, are you running on > > > this GAE? > > > > On Jan 14, 12:28 pm, David Marko <[email protected]> wrote: > > > > > I'm also getting back following error, when web2py tried to create a > > > > new table in FirebirdSQL. > > > > > Traceback (most recent call last): > > > > File "c:\java\google_appengine\web2py\gluon\restricted.py", line 62, > > > > in restricted > > > > exec ccode in environment > > > > File "c:/java/google_appengine/web2py/applications/firebird/models/ > > > > db.py", line 9, in <module> > > > > db=SQLDB('firebird://SYSDBA:master...@localhost:3050/c:/ > > > > firebirdsql/CESTINA.FDB') > > > > File "c:\java\google_appengine\web2py\gluon\sql.py", line 571, in > > > > __init__ > > > > self._execute('SET NAMES UTF8;') > > > > File "c:\java\google_appengine\web2py\gluon\sql.py", line 570, in > > > > <lambda> > > > > self._execute=lambda *a,**b: self._cursor.execute(*a,**b) > > > > ProgrammingError: (-104, 'isc_dsql_prepare: \n Dynamic SQL Error\n > > > > SQL error code = -104\n Token unknown - line 1, column 5\n NAMES') > > > > > David > > > > > On 14 Led, 13:06, David Marko <[email protected]> wrote: > > > > > > For collations (ordering) working properly one have to specify > > > > > 'COLLATE' clause, when creating tables manualy. > > > > > e.g. NAME VARCHAR(100) CHARACTER SET UTF8 COLLATE UNICODE); > > > > > > But its not how web2py generates tables, so ordering the select > > > > > statements doesnt work properly later. > > > > > > David > > > > > > On 14 Led, 12:41, Petros Diveris <[email protected]> wrote: > > > > > > > Hi, > > > > > > > I have done in the not so far past. What is it that you are after? > > > > > > > Petros > > > > > > > On Jan 14, 11:13 am, David Marko <[email protected]> wrote: > > > > > > > > Hello, > > > > > > > is there anyone using web2py with FirebirdSQL database? My > > > > > > > question > > > > > > > leads to some internationalisation issues, correct collations etc. > > > > > > > > David --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
