Re: Unique UUID value - PostgreSQL 9.2

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: "drum(dot)lucas(at)gmail(dot)com" <drum(dot)lucas(at)gmail(dot)com>
Cc: Brent Wood <Brent(dot)Wood(at)niwa(dot)co(dot)nz>, James Keener <jim(at)jimkeener(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Unique UUID value - PostgreSQL 9.2
Date: 2016-03-15 22:16:38
Message-ID: CAKFQuwY1OJs8ySHZkgPiYdibrM6tN5iy8GSOjymW5ki7x4DnLA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Mar 15, 2016 at 2:48 PM, drum(dot)lucas(at)gmail(dot)com <drum(dot)lucas(at)gmail(dot)com>
wrote:

>
>
>>>>
>>> I wouldn't ask if I wouldn't have tested it!
>>>
>>> Will have a look.
>>>
>>> ​
>> I didn't asked if you tested what you did post. I asked if you tried
>> anything else before asking to be fed the answer. If you did it would be
>> nice to include those other attempts.
>>
>> David J.
>> ​
>>
>>
>
>
> It's already working:
>
>> INSERT INTO junk.wm_260_billables2 (account_id, code, info)
>> SELECT account_id, 'test_' || uuid_generate_v4(), info
>> FROM junk.wm_260_billables1;
>
>
> BUT.. I'm getting a very long UUID - Would like some smaller
>
>> test_ea8bacbe-fa3c-4072-b511-643a56feb40e
>
>
SELECT ​'test_'​ || substring(uuid_generate_v4()::text, 1, 1);

Or use a sequence, or just compute "ROW_NUMBER() OVER ()" and tack that on.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Munro 2016-03-15 23:14:05 Re: How to Qualifying or quantify risk of loss in asynchronous replication
Previous Message John R Pierce 2016-03-15 22:01:57 Re: Unique UUID value - PostgreSQL 9.2