Paolo Lucente
Sun, 08 Jun 2008 15:19:06 -0700
Hi Peter, long time no see - hope you're fine. I received a single report of somebody using pmacct with a MySQL cluster but don't know which version and never tried myself - indeed if anybody has anything to share in this sense, good or bad, please don't be afraid! >From the list of constraints listed in your email, i don't see anything clashing with the standard SQK table structure used by pmacct: * no foreign keys, nor TEXT/BLOB fields * no extra long database/table/attribute names * no extra long rows, definitely under 8K * the table has a primary key no further indexes Cheers, Paolo On Sun, Jun 08, 2008 at 11:08:19PM +0200, Pajlatek wrote: > Hi > Has anyone used pmacct on MySQL cluster yet ? And is it possible > knowing the cluster constraints : > * NDB does not support foreign keys or FULLTEXT indexes or indexes on text > columns > (indexes on char/varchar are ok). > * Attribute names are automatically truncated to 31 characters. > Database names and table names can total a maximum of 122 characters > - the maximum length for an NDB table name is 122 characters, > less the number of characters in the name of the database of which that > table is a part. > * The maximum number columns and indexes per table is limited to 128. > * Temporary tables are not supported. > * Every table using the NDBCluster storage engine requires a primary key; > if no primary key is defined by the user, then a ???hidden??? primary key > will be created by NDB. > This hidden primary key consumes 31-35 bytes per table record. > * The maximum permitted size of any one row is 8KB. > Note that each BLOB or TEXT column adds 256 + 8 = 264 bytes towards this > total. > > Thank you for any help > > Peter _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists