From: | Arjen Nienhuis <a(dot)g(dot)nienhuis(at)gmail(dot)com> |
---|---|
To: | Blake Starkenburg <blake(at)oldride(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Column Type Suggestions |
Date: | 2009-10-29 23:21:27 |
Message-ID: | 11ddbd200910291621u79313a09kb29f086aa4bc625b@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Oct 29, 2009 at 9:34 PM, Blake Starkenburg <blake(at)oldride(dot)com> wrote:
> I am in the midst of planning for a new database which will contain specific
> keywords relating to different products. For example a "Microwave" may have
> the keywords HOUSEHOLD -> PANASONIC -> CAROUSEL -> CONVECTION -> 2200 WATTS.
> A pair of Levis may be CLOTHING -> LEVIS -> STONEWASHED -> BOOT CUT ->
> 36x34.
>
> Initially I had planned to use Postgresql's Array Column (keywords
> varchar(100)[]) but this has some limitations when using the LIKE operator,
> making searching for specific string of words difficult unless you know
> firsthand the array key (keywords[2] LIKE 'PANA%').
>
> Does anyone have any suggestions? Product keywords could vary from 1 up to
> 20, maybe more. Performance isn't a huge issue since the database table will
> be fairly small and on a local network. Appreciate all the input! NOTE:
> Using PHP5/Postgresql 8.3
Would ltree fit your problem?
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2009-10-29 23:27:18 | Re: Postgres alpha testing docs and general test packs |
Previous Message | Chris | 2009-10-29 21:55:37 | Re: Column Type Suggestions |