Hi,
the polygon function seems to be limited to
approximately 100 point arguments but some of my
polygons consist of more than 100 points. Are there
any hacks to get around of these limitations? Or do I
really have to install postGIS to deal with such
polygons?
(I am using PostgreSQL 8.1.9 on a L
Hello everybody, I have a question related with sequences.
When I init a sesion with my db, if a do the next sentence:
SELECT currval('pagos_id_pago_seq');
return this:
ERROR: the relation doesn't exist
(or somethimg like that, because the message is in spanish)
but if I
On Fri, Aug 17, 2007 at 04:33:04PM -0500, Judith wrote:
> When I init a sesion with my db, if a do the next sentence:
>
>SELECT currval('pagos_id_pago_seq');
>
>
> return this:
> ERROR: the relation doesn't exist
>(or somethimg like that, because the message is in spanish)
You _must
On 8/17/07, Judith <[EMAIL PROTECTED]> wrote:
> Hello everybody, I have a question related with sequences.
>
> When I init a sesion with my db, if a do the next sentence:
>
> SELECT currval('pagos_id_pago_seq');
>
>
> return this:
>ERROR: the relation doesn't exist
> (or s
=?iso-8859-1?q?Franz=20M=FChlbauer?= <[EMAIL PROTECTED]> writes:
> the polygon function seems to be limited to
> approximately 100 point arguments
Surely not. Please provide a concrete example of your problem.
regards, tom lane
---(end of broadcas
Hi, We have the following three tables.
safety=> SELECT record_id, record_date FROM record;
record_id | record_date
---+
1 | 2007-07-23 11:30:37+10
2 | 2007-07-27 11:30:14+10
3 | 2007-07-17 13:15:03+10
(3 rows)
safety=> SELECT obser
