DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	b=IQb6DhBop7QlQrLtFXfeIOgx82IhkfWNFkdNmzZWfx64mmlkB/H2NVYlhzSaKhhBMN
	0v2YCc73Z9lwxmQbfS5+i5fSjrQWqUgNCM9tbwmTdNHZRAnedOG+dV8QT+IC83nUume6
	q7XfaSX+Q3LErrheSUfk5aaVOlaoTxCtosWWs=
MIME-Version: 1.0
In-Reply-To: <4BBC1B89.5080405@bankir.ru>
References: <n2i5ab13581004061033j4ed25734xd0504cb95a1fc092@mail.gmail.com>
	<4BBC1B89.5080405@bankir.ru>
Date: Wed, 7 Apr 2010 00:17:55 -0600
Message-ID: <k2xdcc563d11004062317g35914f60r49ea20612632b0e3@mail.gmail.com>
Subject: Re: Table Design for Hierarchical Data
From: Scott Marlowe <scott.marlowe@gmail.com>
To: silly sad <sad@bankir.ru>
Cc: Lee Hachadoorian <lee.hachadoorian@gmail.com>,
	pgsql-sql <pgsql-sql@postgresql.org>
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Apr 6, 2010 at 11:43 PM, silly sad <sad@bankir.ru> wrote:
> P.S.
> almost foget, do not try any oracle-like "tree-jouns" or "special types" or
> such a crap.
>
> your problem as plain as to store a pair of integers
> (or numerics (i prefer))

Since it's an identifier and not really a numeric per se, I'd store it
as text.  I mean it could as easily be a 5 character alpha code as 5
character number code.

With tet you can create indexes on substring(idfield,1,1),
substring(idfield,1,2), substring(idfield,1,3),
substring(idfield,1,4), and substring(idfield,1,5) for fast lookups
and matching.