On Feb 2, 2:15 am, Ed Hagen wrote:
> £ukasz, Thanks for your comments.
>
> > Could you describe your current solution in more detail?
>
> Well, my use of the term "solution" was perhaps a bit generous. First,
> I educated my users why this problem was hard to solve. Second, I
> picked a single col
Łukasz, Thanks for your comments.
> Could you describe your current solution in more detail?
Well, my use of the term "solution" was perhaps a bit generous. First,
I educated my users why this problem was hard to solve. Second, I
picked a single collation that everyone could live with. Third, I
On 1 February 2012 20:27, Ed Hagen wrote:
> Hi,
>
> Let me preface this request by saying that when it comes to django,
> I'm an advanced beginner (so this might be a dumb request).
>
> The motivation for my request involved users of a django-based
> database of international scholars who wanted t
Hi,
Let me preface this request by saying that when it comes to django,
I'm an advanced beginner (so this might be a dumb request).
The motivation for my request involved users of a django-based
database of international scholars who wanted their names sorted
"correctly." I explained that differe
On 02/01/2012 10:30 AM, Daniel Moisset wrote:
On Tue, Jan 31, 2012 at 8:34 PM, josharian wrote:
Hi all,
We're using connection.queries to log all sql executed during
development. I find myself wishing that in addition to 'sql' and
'time', there was a 'traceback' entry, so that troublesome/myst
On Tue, Jan 31, 2012 at 8:34 PM, josharian wrote:
> Hi all,
>
> We're using connection.queries to log all sql executed during
> development. I find myself wishing that in addition to 'sql' and
> 'time', there was a 'traceback' entry, so that troublesome/mysterious
> queries could quickly be tracke
