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

Re: Fwd: PostgreSQL questions - copy / paste new data and updating records

From: Jon Erdman <postgresql(at)thewickedtribe(dot)net>
To: Alex Marinov TR <alex(at)tennisround(dot)com>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, "austinpug(at)postgresql(dot)org" <austinpug(at)postgresql(dot)org>
Subject: Re: Fwd: PostgreSQL questions - copy / paste new data and updating records
Date: 2011-09-26 22:04:33
Message-ID: 4E80F6F1.4090807@thewickedtribe.net (view raw or flat)
Thread:
Lists: austinpug
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/26/2011 03:03 PM, Alex Marinov TR wrote:
>
> We have about 20,000 records of tennis facilities. Sometimes people
> call in with updates - new phone, new address, more courts, etc. To my
> surprise I couldn't figure out a way to look up Heather Farm Park,
> Walnut Creek, CA when I opened the table of records in pgAdmin. So I
> don't know how to find that listing to change its phone.
>
> Thanks, Alex

Ah, yes you would use SQL for that, using the query tool:

SELECT * FROM table_name WHERE field_name = 'text value';

or to do a partial string match:

SELECT * FROM my_table WHERE the_address ~ 'Heather';

There might be a way to filter the record view in pgadmin, but I'm not sure.

There's plenty of documentation on the SQL language (as well as lots of
books):

http://www.postgresql.org/docs/9.0/static/sql.html
- --
Jon T Erdman (aka StuckMojo)
    PostgreSQL Zealot

-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk6A9vEACgkQRAk1+p0GhSEifwCfWI8uR24Pfp/hSlfUJOw4zZXN
+z4AnRR1brfV+OvTZGe6GLpX/CnOTpb7
=wLZz
-----END PGP SIGNATURE-----

Attachment: 0x9D068521.asc
Description: application/pgp-keys (2.1 KB)

In response to

austinpug by date

Next:From: cwiserrDate: 2011-10-04 16:43:31
Subject: AustinPUG mtg on Oct 12th @6:30pm
Previous:From: Neal BrownDate: 2011-09-26 20:44:14
Subject: Re: Fwd: PostgreSQL questions - copy / paste new data and updating records

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