Received: from mail.callnetuk.com ([195.13.89.5])
	by hub.org (8.9.3/8.9.3) with SMTP id LAA92422
	for <pgsql-interfaces@postgreSQL.org>;
	Sun, 16 May 1999 11:30:49 -0400 (EDT)
	(envelope-from jscarfe@callnetuk.com)
Received: from callnetuk.com (da129d96.dialup.callnetuk.com[212.67.129.96])by
	WHISKEY(MailMax 2.040) with ESMTP id 0 for
	jscarfe@callnetuk.com; Sun, 16 May 1999 16:40:31 +0100 GDT
Message-ID: <373EE594.D51FE2BE@callnetuk.com>
Date: Sun, 16 May 1999 16:34:44 +0100
From: Julian Scarfe <jscarfe@callnetuk.com>
X-Mailer: Mozilla 4.04 [en] (WinNT; I)
MIME-Version: 1.0
To: pgsql interfaces <pgsql-interfaces@postgreSQL.org>
Subject: Paths in DBD::Pg
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I'd like to deal with geometrical data types, paths in particular,
efficiently in Perl using Pg. But Pg, understadably I suppose, just
returns a path as a scalar string like ((1,2),(3,4),(5,6)). Whereas I
can 'eval' a point fairly efficiently, it's not very efficient to turn a
long string such as the above into an array of arrays.

Am I missing something in the Pg interface that would allow me to get
paths into sensible data structures efficiently?

Julian Scarfe