Re: Runtime accepting build discrepancies

From: Laszlo Hornyak <kocka(at)forgeahead(dot)hu>
To: Thomas Hallgren <thhal(at)mailblocks(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Runtime accepting build discrepancies
Date: 2005-03-11 08:05:45
Message-ID: Pine.LNX.4.58.0503110832240.7382@www.forgeahead.hu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2005-03-11 08:20:00 Re: [HACKERS] We are not following the spec for HAVING without GROUP
Previous Message Tom Lane 2005-03-11 06:48:47 Re: BUG #1528: Rows returned that should be excluded by WHERE clause