Yep, you are right that with Firebird you need to specify the
collation order in advance.
An immediate solution to your problem would be to create the tables
your self, with which ever tool you use (e.g IBExpert) and then in
your model you can do something like
db.define_table('babylon',
SQLField('word', length=2000),
SQLField('definition', 'text'),
migrate=False)
This way you incorporate an existing table into your model.
On the other hand, been able to pass the collation to the SQLField
would be welcome I think.
Hope this helps
Petros
On Jan 14, 12:06 pm, 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
-~----------~----~----~----~------~----~------~--~---
