From: | selkovjr(at)mcs(dot)anl(dot)gov |
---|---|
To: | Julian Scarfe <jscarfe(at)callnetuk(dot)com>, pgsql-interfaces(at)postgreSQL(dot)org |
Subject: | Re: [INTERFACES] Paths in DBD::Pg |
Date: | 1999-05-16 15:29:33 |
Message-ID: | 199905161628.LAA13696@antares.mcs.anl.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
> 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.
You don't need to eval() individual points. If you eval() the whole
thing it will give you one single array:
@a = eval "((1,2),(3,4),(5,6))";
print "@a\n";
--Gene
From | Date | Subject | |
---|---|---|---|
Next Message | Julian Scarfe | 1999-05-16 15:34:44 | Paths in DBD::Pg |
Previous Message | Tom Lane | 1999-05-16 14:36:04 | Re: [INTERFACES] Re: [HACKERS] 6.5 cvs: problem with includes in src/interfaces/libpq++/ |