Re: Change in datetime type casting

Поиск
Список
Период
Сортировка
От Daniele Varrazzo
Тема Re: Change in datetime type casting
Дата
Msg-id CA+mi_8YXzvN6h8uQs4+1M1Evy7KoOfeZoU9QTjzUEy1nGd9TcQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Change in datetime type casting  (Federico Di Gregorio <fog@dndg.it>)
Ответы Re: Change in datetime type casting  (Federico Di Gregorio <fog@dndg.it>)
Re: Change in datetime type casting  (Adrian Klaver <adrian.klaver@gmail.com>)
Список psycopg
On Thu, Jun 28, 2012 at 7:30 AM, Federico Di Gregorio <fog@dndg.it> wrote:
> On 28/06/12 01:19, Adrian Klaver wrote:

>> Note the addition of the casts. This is causing problems when using the
>> hstore adapter as hstore expects a plain string. Is there a way to get
>> around this?
>
> The cast were introduced because PostgreSQL 9.x is much strictier about
> function signatures than the 8.x series. Sometimes functions taking
> parameters were not found because of the implicit text->other type cast.

Hstore is a mapping from strings to strings, not a generic dictionary
mapping. There's never been a promise to adapt generic python
dictionary (mapping hashable -> anything) into it. Even if you ram a
python date into a postgres hstore, reading it back you will get a
string.

You can write a custom adapter to map the datetimes to strings without
the cast and use them into hstore.

-- Daniele

В списке psycopg по дате отправления:

Предыдущее
От: Federico Di Gregorio
Дата:
Сообщение: Re: Change in datetime type casting
Следующее
От: Federico Di Gregorio
Дата:
Сообщение: Re: Change in datetime type casting