Warning: Can't synchronize with repository "(default)" (Unsupported version control system "svn": No module named svn). Look in the Trac log for more information.

Ticket #88 (closed defect: fixed)

Opened 14 years ago

Last modified 12 years ago

Identity somodel should use UnicodeCol instead of StringCol

Reported by: Petr Mifek Owned by: Jeff Watkins
Priority: normal Milestone: 0.9
Component: Identity Version:
Severity: minor Keywords:


turbogears.identity.model.somodel should use UnicodeCol? instead of StringCol?, at least in displayName column and the a-like. If not for anything else, then because the CatWalks? speaks UTF-8 and accepts non-ascii chars in there. In turn then there are some nasty errors in SQLObect about not being able to convert that in ascii...

I think there's no harm at using UnicodeCol? pretty everywhere there. Then it is a great tool for the non-english speaking too ;)

Change History

comment:1 Changed 14 years ago by jeff@…

  • Owner changed from jeff to Jeff Watkins
  • Priority changed from low to normal
  • Milestone changed from 1.0 to 0.9

This is actually a no-brainer. The only reason I used StringCols? is because I haven't got a brain...

comment:2 Changed 14 years ago by jeff@…

  • Component changed from TurboGears to Identity

comment:3 Changed 14 years ago by jeff@…

  • Status changed from new to closed
  • Resolution set to fixed

Changed to use UnicodeCols?.

Note: See TracTickets for help on using tickets.