From: | Arjen Nienhuis <a(dot)g(dot)nienhuis(at)gmail(dot)com> |
---|---|
To: | Mike Christensen <mike(at)kitchenpc(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Query to get the "next available" unique suffix for a name |
Date: | 2010-09-28 07:44:34 |
Message-ID: | AANLkTimQHj1rBdEAx9rdit9SNkD-p_TqYVJ9pcrPKKqi@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> 4) Do a SELECT on each row that starts with "MikeChristensen" and then
> trying to append the row count to the end, this might not be exact but
> it's somewhat intelligent as a starting point. However, this might
> require some special indexes on this table to quickly scan rows that
> start with a certain name. However, if I get to the point where this
> becomes slow then I can worry about it at that point since this would
> only be run on new account creation and not super speed critical.
>
CREATE TABLE test (a text PRIMARY KEY);
INSERT INTO test (a)
SELECT * FROM (SELECT 'MikeChristensen' || generate_series AS t FROM
generate_series(1,10000)) x
WHERE t NOT in (SELECT a FROM test) LIMIT 1 RETURNING *;
Groeten, Arjen
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Christensen | 2010-09-28 07:58:34 | Re: Query to get the "next available" unique suffix for a name |
Previous Message | John R Pierce | 2010-09-28 06:51:50 | Re: Merge replication with Postgresql on Windows? |