On Fri, 12 Mar 2010 22:10:27 -0500, Jay Pipes <[email protected]> wrote: > And I suppose you could even have a MIN_STORE_BYTES and > MAX_STORE_BYTES. That would be quite useful for applications or > scripts doing provisioning and capacity planning, I think :)
We can't really do this in a portable way... as different engines will use different ways of storing things. Doing provisioning calculations is horrifically complex.. just check out ndb_size.pl if you want to be sure :) I'm not sure we should even pretend to help here. just think of ARCHIVE. It cannot give any estimate as to how much space a row may take up - and if you provisioned on MIN_STORE_BYTES (which could be 0 or 1) or MAX_STORE_BYTES (length of field) you'd likely equally be horrifically wrong. -- Stewart Smith _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
