Re: Runtime accepting build discrepancies

Поиск
Список
Период
Сортировка
От Laszlo Hornyak
Тема Re: Runtime accepting build discrepancies
Дата
Msg-id Pine.LNX.4.58.0503110832240.7382@www.forgeahead.hu
обсуждение исходный текст
Ответ на Re: Runtime accepting build discrepancies  (Thomas Hallgren <thhal@mailblocks.com>)
Ответы Re: Runtime accepting build discrepancies  (Thomas Hallgren <thhal@mailblocks.com>)
Список pgsql-hackers
The default should be the default used by PostgreSQL, and the extra ones
should be commented out under it.
Not the most user friendly solution, but can we do anything else?

Laszlo

On Fri, 11 Mar 2005, Thomas Hallgren wrote:

> Laszlo Hornyak wrote:
>
> > IMHO this is why decoupling is good and neccesary. If one configures
> > the RDBMS to use different another of data, then I simply replace a
> > couple of lines in the data mapping configuration. In the case of
> > custom datatypes in PostgreSQL, the same happens. This is no code
> > modification nor recomplitation in PL-J, only a reconfiguration.
> > This is why I have sent that link, but this configuration file
> > fragment may explain it better:
> >    <typemapper>
> >        <map>
> >                <type db="timestamp"
> > class="org.pgj.typemapping.postgres.PGTimestamp"/>
> >                <!-- type db="timestamp"
> > class="org.pgj.typemapping.postgres.PGTimestampINT64"/ -->
>
> Sure Laszlo. That solves everything. But where do you get the
> information on what to comment out and what to use in the first place?
>
> Regards,
> Thomas Hallgren
>


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

Предыдущее
От: Nicolai Tufar
Дата:
Сообщение: Re: [pgsql-hackers-win32] snprintf causes regression tests to fail
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: Re: We are not following the spec for HAVING without GROUP