| From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: bigint out of range |
| Date: | 2019-05-18 20:19:22 |
| Message-ID: | bc9cd95b-6ff8-891d-819e-6e947dec7fd1@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 5/18/19 2:27 PM, Peter J. Holzer wrote:
> On 2019-05-18 10:49:53 -0700, David G. Johnston wrote:
>> On Saturday, May 18, 2019, Peter J. Holzer <hjp-pgsql(at)hjp(dot)at> wrote:
>>
>> On 2019-05-16 08:48:51 -0700, David G. Johnston wrote:
>> > On Thu, May 16, 2019 at 8:31 AM Daulat Ram <Daulat(dot)Ram(at)exponential(dot)com>
>> wrote:
>> >
>> >
>> > url_hash | bigint | | not null |
>> >
>> >
>> > Change the type of url_hash; make it text instead of bigint.
>>
>> Or numeric(38, 0). I think it isn't coincidence that he tries to store
>> a 38-digit number in it.
>>
>>
>> You don’t perform math on a hash
> That's not generally true. Hashes are used for further computation for
> example in hash tables or in cryptography.
How is it "using math" to use a hash key in a hash lookup table?
--
Angular momentum makes the world go 'round.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter J. Holzer | 2019-05-18 20:49:41 | Re: bigint out of range |
| Previous Message | Peter J. Holzer | 2019-05-18 19:27:03 | Re: bigint out of range |