#2416: Spurious SAWarnings caused by built-in SQL-based auth
------------------------+---------------------------------------------------
Reporter: pitrou | Owner:
Type: defect | Status: new
Priority: normal | Milestone: 2.1b2
Component: TurboGears | Version: 2.1a1
Severity: normal | Resolution:
Keywords: |
------------------------+---------------------------------------------------
Comment (by Gustavo):
Replying to [comment:3 chrisz]:
> To solve the first problem, we would need to convert ascii (str) values
to unicode whenever we are using them in SQLAlchemy filter comparisons. As
far as I see this happens at the following places:
>
> * method `_get_section_as_row` in repoze.wha.plugins.sql.adapters
> * method `_get_item_as_row` in repoze.wha.plugins.sql.adapters
> * method `get_user` in repoze.who.plugins.sa
Those methods should work with both ASCII and Unicode values, since they
don't change or rely on a particular type of string.
I think this issue will be gone with #2438 too.
--
Ticket URL: <http://trac.turbogears.org/ticket/2416#comment:4>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en