On Sun, 2006-08-06 at 02:48 -0700, Aaron Stone wrote: > On Fri, 2006-08-04 at 20:11 +0200, [EMAIL PROTECTED] wrote: > > > ---------------------------------------------------------------------- > > jnorell - 04-Aug-06 20:11 > > ---------------------------------------------------------------------- > > Yeah, cutting down to 90 gets that to run. To size the correctly, what's > > the largest (in # digits) numbers that would ever be there? We've got 9 > > digits, but if you had 10, that would again go over the 1024 chars. > > Turns out that limits.h says we have to handle up to this: > > #define ULLONG_MAX 18446744073709551615ULL > > That's 20 digits by my count... I guess I'll cut the list down to 40 > items in the query?
With the current schema we just have to cover the largest of postgres's INT8, mysql's bigint(21) or sqlite's INTEGER, right? Eg. mysql's bigint can be +/-9223372036854775807... which again is 20 chars. :) So yeah, that's probably "right". -- Jesse Norell - [EMAIL PROTECTED] Kentec Communications, Inc.
