2013/7/10 Stewart Smith <stewart@flamingspork.com>
Roberto Spadim <roberto@spadim.com.br> writes:
> well, another doubts that i had some time ago reading unireg source...
>
> 1)why it have a 64k limit? that's a logical limit (a limit in int variable
> or char or something like it)? or just a "well i think 64k is a good
> 'constant' limit"?

2^16 is why there's that limit.
ok but why 2^16? it's based in some structure with a variable type that can't handler > 2^16 bytes? or just a number like 65555 65554 65553... ?

 
> 2)why we "still" with this "old" unireg format?
> i know that someone must start the new format and it will not be compatible
> with mysql...
> but there's any raw idea or a issue in mdev or lauchpad about changing .frm
> format or creating a new one?
>
> maybe something more human readable YAML or JSON, and a space for engine
> information https://mariadb.atlassian.net/browse/MDEV-3936

See my other post: Drizzle has a protobuf based format. It's non trivial
to make the server behave with this though. It appears there's some code
in MariaDB to construct server data structures from a SQL statement
though, so perhaps that's more usable.

--
Stewart Smith
humm i read something about protobuf, but is it human readable? 
i see yaml and json more common to web standards but they don't have a 'xml schema', while protobuf have a optional / required
other doubt, does this increase open/close expend time? for example, today frm = 0.1ms, protobuf=1ms, or something like it? or file parse time isn't the main time consume open/close expend time?


--
Roberto Spadim
SPAEmpresarial