Comments on: Base36 Conversion in PostgreSQL http://www.rightbrainnetworks.com/blog/base36-conversion-in-postgresql/ Thu, 11 Aug 2011 13:49:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jamie http://www.rightbrainnetworks.com/blog/base36-conversion-in-postgresql/comment-page-1/#comment-742 Jamie Thu, 11 Aug 2011 13:49:00 +0000 http://blog.rightbrainnetworks.com/?p=148#comment-742 Thanks for the feedback! Thanks for the feedback!

]]> By: Robert http://www.rightbrainnetworks.com/blog/base36-conversion-in-postgresql/comment-page-1/#comment-741 Robert Thu, 11 Aug 2011 13:11:33 +0000 http://blog.rightbrainnetworks.com/?p=148#comment-741 Another limitation of this code is - it supports only half of possbible bigint values (only positive ones). When ret overflows - function returns exception. Another limitation of this code is – it supports only half of possbible bigint values (only positive ones). When ret overflows – function returns exception.

]]> By: Robert http://www.rightbrainnetworks.com/blog/base36-conversion-in-postgresql/comment-page-1/#comment-740 Robert Wed, 10 Aug 2011 10:52:59 +0000 http://blog.rightbrainnetworks.com/?p=148#comment-740 Your base36_decode contains bug in string: ret := ret + (val * (36 ^ i)); For large numbers (for example, select * from base36_decode('324adc6a6ds')); it returns ERROR: invalid input syntax for integer: "1.11836923491136e+16" CONTEXT: PL/pgSQL function "base36_decode" line 17 at assignment Mentioned string must be fixed as follows: ret := ret + (val * (36 ^ i))::bigint; After that all works ok, thanks for sharing your code. Your base36_decode contains bug in string:

ret := ret + (val * (36 ^ i));

For large numbers (for example,
select * from base36_decode(’324adc6a6ds’));

it returns
ERROR: invalid input syntax for integer: “1.11836923491136e+16″
CONTEXT: PL/pgSQL function “base36_decode” line 17 at assignment

Mentioned string must be fixed as follows:
ret := ret + (val * (36 ^ i))::bigint;

After that all works ok, thanks for sharing your code.

]]> By: PK http://www.rightbrainnetworks.com/blog/base36-conversion-in-postgresql/comment-page-1/#comment-734 PK Sat, 28 May 2011 16:22:34 +0000 http://blog.rightbrainnetworks.com/?p=148#comment-734 Would you have a C equivalent of this? Doing this in pl/pgsql is going to be a major hit. Thanks! Would you have a C equivalent of this? Doing this in pl/pgsql is going to be a major hit.

Thanks!

]]> By: Jamie http://www.rightbrainnetworks.com/blog/base36-conversion-in-postgresql/comment-page-1/#comment-696 Jamie Wed, 04 Aug 2010 16:52:12 +0000 http://blog.rightbrainnetworks.com/?p=148#comment-696 Certainly. You may use it in anyway you wish; no attribution is necessary. Though, as I mentioned in the original posting, you may want to test the performance of the functions or maybe even reconsider whether this is a task that should be done within the DB. Certainly. You may use it in anyway you wish; no attribution is necessary. Though, as I mentioned in the original posting, you may want to test the performance of the functions or maybe even reconsider whether this is a task that should be done within the DB.

]]> By: P http://www.rightbrainnetworks.com/blog/base36-conversion-in-postgresql/comment-page-1/#comment-695 P Tue, 03 Aug 2010 22:40:57 +0000 http://blog.rightbrainnetworks.com/?p=148#comment-695 May I use these in a commercial project? If so may I make changes if attribution is provided? May I use these in a commercial project? If so may I make changes if attribution is provided?

]]> By: P http://www.rightbrainnetworks.com/blog/base36-conversion-in-postgresql/comment-page-1/#comment-694 P Tue, 03 Aug 2010 22:39:48 +0000 http://blog.rightbrainnetworks.com/?p=148#comment-694 May I use this in some commercial work I've been doing? If so may I make changes if attribution is given? May I use this in some commercial work I’ve been doing? If so may I make changes if attribution is given?

]]>