On 3 Jun 2015, at 8:54pm, Justin Clift wrote:
> It looks like the SourceForge admin staff have taken control
> of the "sqlite" project on SourceForge:
>
> http://sourceforge.net/mirror/sqlite/
Don't worry about it. As the page says, the SourceForge page on SQLite is just
a mirror rather
Hi all,
It looks like the SourceForge admin staff have taken control
of the "sqlite" project on SourceForge:
http://sourceforge.net/mirror/sqlite/
The owners there are now "sf-editor1" and "sf-editor2".
Any idea if this is a recent thing, related to their other
string of project seizures?
I can see why they're doing it as well. Some people have different
preferences to grab the repo. I have a script running on one of my linux
boxes that checks periodically (Once a week? Once a month? I can't
remember) for all links on the SQLite download page. If I don't have the
URL or file
___
?smail Keskin
ismail.keskine at gmail.com
cep : 0532 576 8488
On Wed, Jun 03, 2015 at 03:55:04PM -0700, Darko Volaric wrote:
> I've tackled this problem from a couple of different angles. My goal was to
> allow arbitrary user defined types, based on the builtin types (essentially
> subtypes of the existing types), with a minimum of work and minimum
>
Check out cubeSQL Admin from sqlabs.com.? This turns SQLite into a
server; you can use the cubeSQL ODBC driver to connect to it from other
computers, among other methods.
[1] https://github.com/planetopendata/awesome-sqlite
Sourceforge is rapidly digging its own grave with its awful behavior. It's
hardly "taken control" of the project, it's just another fork, essentially.
SQLite isn't even copyrighted and has no licence, so no problem there.
Using the SQLite trademark might be a problem though.
On Wed, Jun 3, 2015
Yep, references a another one. Just like the functions, you have to join on
the user type information, add it to constraints, etc.
In my case I'm already modifying and maintaining my own version of SQLite.
My project is basically a database with a lot of extensions. Submitting
patches is not an
I think the difficulty here is that the optimizer is oriented toward the
"low level" and mainly concerned with choosing indexes, processing order
etc (see https://www.sqlite.org/optoverview.html ) and has sort of a
narrow view of the task.
Approaching it from the other end and breaking down the
I've tackled this problem from a couple of different angles. My goal was to
allow arbitrary user defined types, based on the builtin types (essentially
subtypes of the existing types), with a minimum of work and minimum
disruption of the normal/existing use of the database and API.
The approaches
Is it possible to force the creation of an automatic covering index for a
subquery?
Like, 'cross join' can force the join order, 'indexed by' can force index
use on a table, but it doesn't seem like there's anything to force the
creation of an automatic index.
The reason that I ask is that one
On 05/15/2015 02:37 PM, Milan K??? wrote:
> Hello,
> I've found that SQLite is preparing new FTS5 extension, which could be
> better than current FTS3/4.
> If it is still in development, I would like to propose one more
> change. In our project we would need possibility to specify which columns
Hi,
I'm wanting to store data in a way such that I can choose a time in the
past and view records as they were at that dateTime. Therefore (in my
mind), all updates are really inserts with a timestamp. Ids are suddenly
no longer primary keys, as many records can have the same id, but a new
13 matches
Mail list logo
