On 3/13/06, Jonas Oreland <jonas@stripped> wrote:
>
> The used space is most likely much smalled in 5.1 that 5.0, but...
> I could imagin that ndb does not properly reports used space when using newly added
> feature varsize.
> The stuff reported is most likely only the fixed part of the record (which used to be
> all there was).
>
> You could/should file a bug report on this...
when i start with an empty db and run an app that runs until the db is
full. the above query starts out returning 0 and immediately jumps to
3.5 (when there's only about 50 rows in the db) and stays at 3.5 until
the db is full around 4k rows. this is a test ndb cluster with data
and index size set to 10Megs. doing the same for index_length returns
0 regardless of what's in the db. this is with 5.0.18.
--
-rm