pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Devin Whalen <devin@synapticvision.com>
To: Jeff Eckermann <jeff_eckermann@yahoo.com>
To: mail@joeconway.com
Cc: pgsql-sql@postgresql.org
Subject: Re: Converting a plperlu function to a plpgsql function
Date: Thu, 22 Jul 2004 15:18:25 -0400
Message-ID: <1090523904.7474.195.camel@192.168.1.80> (raw)
In-Reply-To: <20040722190916.89900.qmail@web20824.mail.yahoo.com>
References: <20040722190916.89900.qmail@web20824.mail.yahoo.com>

On Thu, 2004-07-22 at 15:09, Jeff Eckermann wrote:
> --- Joe Conway <mail@joeconway.com> wrote:
> > Devin Whalen wrote:
> > > First line:
> > > my @active_tables=split(/,/,$tables);
> > > 
> > > Is there anyway to split a variable like the perl
> > split above?
> > 
> > I'm no perl guru, but in 7.4 I believe this does
> > what you're looking for:
> > 
> > regression=# select string_to_array('1,2,3',',');
> >   string_to_array
> > -----------------
> >   {1,2,3}
> > (1 row)
> > 
> > > Second line:
> > > 
> > >  if ($r=~/^-([0-9]?)([A-z_]+)/)
> > >  {
> > >     my $locid = $1;
> > >     my $table = $2;
> 
> PostgreSQL doesn't offer capturing parentheses.  The
> regex library does offer that, but no-one has yet done
> the coding to bring that functionality into
> PostgreSQL.
> 
> You could do it in two steps:
> 1. Test using a regular expression
> 2. locid := substr(r,1); table := substr(r,2,1-len(r))
> (better check the syntax on those).
> 
> > 
> > Not sure about this one. Hopefully someone else can
> > chime in. Maybe a 
> > little less efficient, but it seems like it would be
> > easy enough to 
> > parse when true.
> > 
> > HTH,
> > 
> > Joe
> > 
> > ---------------------------(end of
> > broadcast)---------------------------
> > TIP 1: subscribe and unsubscribe commands go to
> > majordomo@postgresql.org
> > 
> 
> 
> 
> 		

Hey,

Thanks for the advice guys.  The main reason that we wanted to change
from a perl function was because we were having problems getting the
perl library installed for postgres.  We think we have solved that
problem so it looks like I won't have to convert the function.  However,
your responses have made me  realize that I can convert it.  So I think
I will convert it because it saves having to connect up to the database
from inside the perl function.  This might be a little faster??

Thanks for the help.

Later

-- 
Devin Whalen
Programmer
Synaptic Vision Inc
Phone-(416) 539-0801
Fax- (416) 539-8280
1179A King St. West
Toronto, Ontario
Suite 309 M6K 3C5
Home-(416) 653-3982



view thread (5+ messages)  latest in thread

Message-ID: <1090523904.7474.195.camel@192.168.1.80>
Permalink:  ../1090523904.7474.195.camel@192.168.1.80/
Also on:    postgresql.org/message-id/1090523904.7474.195.camel@192.168.1.80

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: devin@synapticvision.com, jeff_eckermann@yahoo.com, mail@joeconway.com
  Subject: Re: Converting a plperlu function to a plpgsql function
  In-Reply-To: <1090523904.7474.195.camel@192.168.1.80>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox