The Xerial JDBC driver does not if I recall correctly. There’s no reason why it
couldn’t, the developers just didn’t implement it. Perhaps you should file an
enhancement request in their issue tracker requesting it be implemented.
If you don’t need nested transactions then you can get a single
Sounds like you're passing a non utf-8 encoded string from C# directly
to sqlite.
The easiest way I know of to check the actual data in the database is to
dump it as hex (i.e., select hex(column_name)) and check if the contents
are what you expect or not.
Gut feeling is that the strings in
Original Message- From:
sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Pepijn Van
Eeckhoudt Sent: 2013年11月25日 16:09 To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Does sqlite has db file-size restriction on
Solaris 10? On 2013-11-23 02:03, L
On 2013-11-23 02:03, Liang Kunming wrote:
java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database
(no such table: tasks)
at org.sqlite.DB.newSQLException(DB.java:383)
at org.sqlite.DB.newSQLException(DB.java:387)
at org.sqlite.DB.throwex(DB.java:374)
Is datetime special in thuis context or will constant expression hoisting like
this happen for any function?
Pepijn
> Op 22-nov.-2013 om 15:35 heeft Richard Hipp het volgende
> geschreven:
>
> The www.sqlite.org server logs are stored in an SQLite database (of
> course). We
On 18 Nov 2013, at 06:13, Simon Slavin wrote:
> On 18 Nov 2013, at 3:38am, Peter Aronson wrote:
>
>> It might be simpler to simply specify a minimum release of SQLite that must
>> be supported,
>
> Actually this is how lots of apps specify their file
> For Peter & Pepijn - I think the issue is essentially a forward-compatibility
> problem moreso than a backward-compatibility one. So I think your idea on
> introducing some version control would be the least painful.
Indeed. The lack of rowid itself is not an issue. It's that someone could
Will without rowid introduce a new schema version number?
If so, we’ll be ok since GeoPackage requires schema version 4.
Pepijn
On 15 Nov 2013, at 16:33, Peter Aronson wrote:
> One additional thing not listed in this document -- use of a internal rowid
> alias (OID, ROWID
On 15-11-13 12:47, Luís Simão wrote:
SQLite answers those question in:
http://www.sqlite.org/draft/withoutrowid.html
Thanks for the pointer. That answered all my questions.
Pepijn
BR
___
sqlite-users mailing list
sqlite-users@sqlite.org
I've been looking into the upcoming 'without rowid' feature
implementation to assess if it will have any impact on the OGC
GeoPackage specification.
One of the things I was wondering is what the intended use case of this
feature is. Does it provide a performance boost and/or space savings? If
On 07 Sep 2013, at 02:03, Peter Aronson wrote:
> Ah, I see. Yeah, that would be trickier. You could save off the geometry
> blob and the GEOSPreparedGeometry object in a structure passed in to
> sqlite3_create_function and accessed via sqlite3_user_data and memcmp each
>
tant. Then all the GeomFromText has to do
> is to return the Geometry blob when sqlite3_get_auxdata returns non-NULL.
>
> Peter
>
> - Original Message -
>> From: Pepijn Van Eeckhoudt <pep...@vaneeckhoudt.net>
>> To: sqlite-users@sqlite.org
>> Cc:
>>
On 06 Sep 2013, at 17:51, Simon Davies wrote:
>> Are there any other ways to kind of memoize the GeomFromText function
>> (or the parameters to distance) besides aux_data?
>
> select Distance( constGeom, geometry ) from table, (select
> GeomFromText('Point(13.457
On 06 Sep 2013, at 17:58, Dominique Devienne wrote:
>> select Distance( constGeom, geometry ) from table, (select
>> GeomFromText('Point(13.457 3)') as constGeom );
>
> Clever. Thanks for that.
Simple and elegant. Thanks for the idea, I'll give it a try.
> Or make your
Hi,
In the extension I'm developing (https://bitbucket.org/luciad/libgpkg)
I'm currently adding support for queries like:
select Distance(
GeomFromText('Point(13.457 3)'),
geometry
) from table;
GeomFromText takes a string and outputs a geometry blob
Distance takes two geometry blobs and
On vr, 2013-08-30 at 09:09 -0400, Richard Hipp wrote:
> On Thu, Aug 29, 2013 at 3:53 AM, Pepijn Van Eeckhoudt <
> pep...@vaneeckhoudt.net> wrote:
> Recently the extension loader was enhanced (I think for 3.7.17) so that it
> tries the first naming schema first, then if t
http://www.sqlite.org/loadext.html states that:
...omitting the second argument for the load_extension() SQL
interface - and the extension loader logic will attempt to
figure out the entry point on its own. It will first try the
generic extension name
http://www.sqlite.org/loadext.html states that:
...omitting the second argument for the load_extension() SQL
interface - and the extension loader logic will attempt to
figure out the entry point on its own. It will first try the
generic extension name
lgende
geschreven:
> On 05/31/2013 09:28 PM, Pepijn Van Eeckhoudt wrote:
>> Sorry for the non-threaded reply. My subscription was set to digest mode...
>>
>> Patch is available at
>> https://dl.dropboxusercontent.com/u/105584447/android_largefile.patch
> Thanks for the p
Sorry for the non-threaded reply. My subscription was set to digest mode...
Patch is available at
https://dl.dropboxusercontent.com/u/105584447/android_largefile.patch
Pepijn
___
sqlite-users mailing list
sqlite-users@sqlite.org
and the
corresponding 64 bit variants of functions must be used (ftruncate64,
pread64, pwrite64, ...).
The attached patch modifies os_unix.c to count less on off_t being a 64-bit
value. Could someone review this and if approved integrate this upstream?
Sincerely,
Pepijn Van Eeckhoudt
21 matches
Mail list logo