Dear developers,
many tricks were discussed here,
and many feature requests generated.
Every discussed problem ALREADY have solution in the current version of the
SQL. Most of the problems are forced by incorrect design of a database !
I ask you:
do not burden the PostgreSQL with features !!! P
Dan Field wrote:
On 24 May 2004, at 14:37, Tom Lane wrote:
Dan Field <[EMAIL PROTECTED]> writes:
I have a similar problem with just one of my queries (although it isn't
a sub select):
You really ought to vacuum and/or analyze occasionally. The EXPLAIN
results show that the planner hasn't got any
On 24 May 2004, at 14:37, Tom Lane wrote:
Dan Field <[EMAIL PROTECTED]> writes:
I have a similar problem with just one of my queries (although it
isn't
a sub select):
You really ought to vacuum and/or analyze occasionally. The EXPLAIN
results show that the planner hasn't got any non-default stati
hook <[EMAIL PROTECTED]> writes:
> What's the proper way to include the suport files for building 'C' trigger
> functions in to the normal PostgreSQL install?
>
>
> I.E. /
> "make install "does not include internal/postgres_fe.h, executor/spi.h
> nor commands/trigger.h in to /usr/local/pgsql
Do you really need MANY-TO-MANY between customers and projects?
I can see customers owning many projects, but do you really have
projects belonging to many customers?
If not, fold cust_proj into projects.
Otherwise, UNIQUE (cp_id, stall_no) on stalls should be enough.
Andreas wrote:
Hi folks,
Is
Bruno Wolff III wrote:
On Wed, May 26, 2004 at 05:13:14 +0200,
Andreas <[EMAIL PROTECTED]> wrote:
Is there a way to have something like this : UNIQUE (table_1.id,
table_2.xxx)
Postgres doesn't support database constraints at this time which is
what you would need to do this simply.
You can enfo
On Wed, May 26, 2004 at 05:13:14 +0200,
Andreas <[EMAIL PROTECTED]> wrote:
>
> Is there a way to have something like this : UNIQUE (table_1.id,
> table_2.xxx)
Postgres doesn't support database constraints at this time which is
what you would need to do this simply.
You can enforce this const
What's the proper way to include the suport files for building 'C'
trigger functions in to the normal PostgreSQL install?
I.E. /
"make install "does not include internal/postgres_fe.h,
executor/spi.h nor commands/trigger.h in to /usr/local/pgsql/include.
---(end of br
