> On Feb 4, 2004, at 3:48 PM, D. Richard Hipp wrote:
> > SQLite seeks to avoid unnecessary feature creep. It also seeks
> > to be small and compact. Adding new built-in functions, especially
> > obscure functions such as md5/md5sum, does not seem compatible with
> > those goals. For SQLite users
On Feb 4, 2004, at 3:48 PM, D. Richard Hipp wrote:
SQLite seeks to avoid unnecessary feature creep. It also seeks
to be small and compact. Adding new built-in functions, especially
obscure functions such as md5/md5sum, does not seem compatible with
those goals. For SQLite users who need md5/md5s
b.bum wrote:
Any reason that [md5sum] isn't included as a normal part of the
sqlite installation/api?
SQLite seeks to avoid unnecessary feature creep. It also seeks
to be small and compact. Adding new built-in functions, especially
obscure functions such as md5/md5sum, does not seem compatible
Enclosed patch adds md5() as an aggregate. Unit tests refactored to
use md5() as opposed to md5sum(). All tests pass [that did before].
I broke the core md5 functions out into a header file full of static
inlines. This reduces namespace pollution while still allowing the
same code to be used
b.bum wrote:
> I'm curious as to why the md5sum() aggregate is only available for the
> purposes of unit testing.
>
> It seems like a fairly generically useful feature in a number of
> contexts. Any reason that it isn't included as a normal part of the
> sqlite installation/api?
Also, might I re
I'm curious as to why the md5sum() aggregate is only available for the
purposes of unit testing.
It seems like a fairly generically useful feature in a number of
contexts. Any reason that it isn't included as a normal part of the
sqlite installation/api?
It would look to mostly be a matter o
6 matches
Mail list logo
