Skip site navigation (1) Skip section navigation (2)

Re: Out of Memory and Configuration Problems (Big Computer)

From: Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>
To: Tom Wilcox <hungrytom(at)googlemail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Out of Memory and Configuration Problems (Big Computer)
Date: 2010-05-28 23:34:33
Message-ID: 53B87E74-2505-4C34-8C96-450B7BA8C41E@solfertje.student.utwente.nl (view raw or flat)
Thread:
Lists: pgsql-general
On 28 May 2010, at 20:39, Tom Wilcox wrote:

>     out = ''
>     for tok in toks:
>         ## full word replace
>         if tok == 'house' : out += 'hse'+ADDR_FIELD_DELIM
>         elif tok == 'ground' : out += 'grd'+ADDR_FIELD_DELIM
>         elif tok == 'gnd' : out += 'grd'+ADDR_FIELD_DELIM
>         elif tok == 'front' : out += 'fnt'+ADDR_FIELD_DELIM
>         elif tok == 'floor' : out += 'flr'+ADDR_FIELD_DELIM
>         elif tok == 'floors' : out += 'flr'+ADDR_FIELD_DELIM

Not that it would solve your problems, but you can write the above much more elegantly using a dictionary:

# normalize the token
try:
	out += {
		'house'		: 'hse',
		'ground'	: 'grd',
		'gnd'		: 'grd',
		'front'		: 'fnt',
		'floor'		: 'flr',
		...
	}[tok]
except KeyError:
	out += tok

# add a field delimiter if the token isn't among the exceptions for those
if tok not in ('borough', 'city', 'of', 'the', 'at', 'incl', 'inc'):
	out += ADDR_FIELD_DELIM

You should probably define those lists outside the for-loop though, I'm not sure the Python interpreter is smart enough to declare those lists only once otherwise. The concept remains though.

Alban Hertroys

--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.


!DSPAM:737,4c00531510211149731783!



In response to

pgsql-general by date

Next:From: Tom WilcoxDate: 2010-05-29 00:43:48
Subject: Re: Out of Memory and Configuration Problems (Big Computer)
Previous:From: Adrian KlaverDate: 2010-05-28 21:58:50
Subject: Re: there is a way to deactivate type validation on 8.3.1????

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group