Postgresql type casting (ex: column::datatype) creates an exception

[niparis]

using the following query :

SELECT creationtime::date, name
FROM question.questionnaires
ORDER BY creationtime DESC;

will give the following exception: TypeError: tuple indices must be integers or slices, not str

because anosql will internally change the sql to :

SELECT creationtime:%(date)s, name 
FROM question.questionnaires 
ORDER BY creationtime DESC;

[alysbrooks]

I think I wrote the code responsible, so I can take a look this weekend. :)

[taidan19]

Ran into this one myself. It was rather curious, because the regex responsible for this in the anoaql code looks like this:

re.sub(r':([a-zA-Z_-]+)', r'%(\1)s', query)

I thought it was rather curious, as I wasn't sure what it's purpose was for. The only time I've ever seen a single colon used in Postgres is for array slicing.

[alysbrooks]

If I remember correctly, using a colon before a name is an anosql convention for parameters (maybe adopted from yesql?) that are being inserted from Python. E.g., WHERE user = :username would make :username a keyword argument in the generated function.

[honza]

I merged the fix. Would you mind testing it?

[nackjicholson]

We should check this against the big regex PR I had merged #25