From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: [PATCH 1/1] sqlite3: Add support for column metadata API, bumped PR
Date: Wed, 06 Nov 2013 16:57:47 +0000 [thread overview]
Message-ID: <527A750B.1020803@dynamicdevices.co.uk> (raw)
In-Reply-To: <CAJTo0LbA64DxS2dp0h3LHTxkm709CiO73Nv3mYtxP3iQwnjF-w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2145 bytes --]
On 06/11/2013 15:46, Burton, Ross wrote:
> On 6 November 2013 15:32, Alex J Lennon <ajlennon@dynamicdevices.co.uk> wrote:
>> +PR = "r1"
> No need to bump PR in oe-core,
OK - this should be reverted/removed then?
> and please explain why enabling column
> metadata is good and what the tradeoffs are.
I found that Mono.Data.SQlite has a dependency on the column meta-data
API, thus enabling this API enables use of Hibernate / Mono with SQLite
and no doubt enables other ORMs / utility libraries.
ref: https://bugzilla.xamarin.com/show_bug.cgi?id=6333
The API is present in the used SQLite3 sqlite-autoconf-3080002
source-base. Thus we are enabling pre-existing SQLite support rather
than introducing new code.
I am not aware of any issues that enabling this SQLite functionality
introduces, other than a slightly increased library size of circa 1.5KB
, i.e. coretexa9_vfp_neon i.MX6
- with column meta-data API 610360 libsqlite3.so.0.8.6
- without column meta-data API 608880 libsqlite3.so.0.8.6
BR, Alex
> Ross
>
>
--
Dynamic Devices Ltd <http://www.dynamicdevices.co.uk/>
Alex J Lennon / Director
1 Queensway, Liverpool L22 4RA
mobile: +44 (0)7956 668178
Linkedin <http://www.linkedin.com/in/alexjlennon> Skype
<skype:alexjlennon?add>
This e-mail message may contain confidential or legally privileged
information and is intended only for the use of the intended
recipient(s). Any unauthorized disclosure, dissemination, distribution,
copying or the taking of any action in reliance on the information
herein is prohibited. E-mails are not secure and cannot be guaranteed to
be error free as they can be intercepted, amended, or contain viruses.
Anyone who communicates with us by e-mail is deemed to have accepted
these risks. Company Name is not responsible for errors or omissions in
this message and denies any responsibility for any damage arising from
the use of e-mail. Any opinion and other statement contained in this
message and any attachment are solely those of the author and do not
necessarily represent those of the company.
[-- Attachment #2.1: Type: text/html, Size: 5043 bytes --]
[-- Attachment #2.2: ddlogo-4.png --]
[-- Type: image/png, Size: 3997 bytes --]
[-- Attachment #2.3: linkedin.png --]
[-- Type: image/png, Size: 631 bytes --]
[-- Attachment #2.4: skype.png --]
[-- Type: image/png, Size: 800 bytes --]
next prev parent reply other threads:[~2013-11-06 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 15:32 [PULL] [PATCH 0/1] sqlite3: Add support for column metadata API Alex J Lennon
2013-11-06 15:32 ` [PATCH 1/1] sqlite3: Add support for column metadata API, bumped PR Alex J Lennon
2013-11-06 15:46 ` Burton, Ross
2013-11-06 16:57 ` Alex J Lennon [this message]
2013-11-06 17:00 ` Burton, Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=527A750B.1020803@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--cc=poky@yoctoproject.org \
--cc=ross.burton@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.