On May 20, 9:01 am, Justin Bronn <[EMAIL PROTECTED]> wrote:
> I'm with Malcolm on not supporting this feature of
> automatically casting to string because the database is doing the
> "right thing" here. [1]
It's certainly the right thing to do in general.
I'd like to mention one use of the impl
> I see that the Oracle backend already includes
> OracleQueryconvert_values which does conversion into the backend based
> on the the passed value and the field type.
>
> Perhaps we need to add that for PostgreSQL now? It's pretty onerous
> to do the casting at the app level.
>
The `convert_val
On Mon, May 19, 2008 at 9:50 AM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
>
> Prior to PostgreSQL 8.3, non-text types were implicitly converted to text.
>
> This allowed things like the following:
>
> class Log(models.Model):
> actor = models.CharField(...)
>
>
> >>> Log.objects.filter(actor=1).c
Prior to PostgreSQL 8.3, non-text types were implicitly converted to text.
This allowed things like the following:
class Log(models.Model):
actor = models.CharField(...)
>>> Log.objects.filter(actor=1).count()
===
With 8.3, this fails because there's no operator between text and integer.
