On 7 Mar 2016, at 11:32 PM, Noel Grandin <noelgrandin@gmail.com> wrote:
On 2016/03/07 2:11 PM, Lionel Elie Mamane wrote:
On Mon, Mar 07, 2016 at 08:23:53AM +0200, Noel Grandin wrote:
A few examples of how SQLite differs from the SQL standard (be it de facto
or de jure standard) in quite deep, fundamental ways:
* lack of other datatypes than "integer", "real" (float), "string of characaters"
and "string of bytes": the basic ones are dates, times, timestamps.
* lack of datatype checking; one can insert "noel" in a column of
type "integer"
* type attached to value, not to column
That is true, but we could implement basic checking of our own on top of that, or just ignore it,
and rely on the user getting it right most of the time (which they normally do). And when they
don't, it is a rather soft failure mode in SQLite.
Also annoying, but can be worked around:
Yeah, that's what I mean - there are other issues, but they can be worked around.
I suppose we can just keep limping along with our current state of affairs, it's not like Base is
that widely used, or particularly vital to our future.
But it would be nice to upgrade to something a little more modern, and Firebird is not really
working out for us, and what other options do we really have?
At least SQLite is widely used and moving forward at a reasonable rate.
Regards, Noel.
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.