[sqlite] Andl: release of recursive queries

The latest release of Andl supports recursive queries. There are sample programs for org chart, Mandelbrot set and a Sudoku solver. You can read about it as http://www.andl.org/posts/ or get it from GitHub https://github.com/davidandl/Andl. Regards David M Bennett FACS Andl - A New Database

[sqlite] Mozilla wiki 'avoid SQLite'

I agree. It would be relatively easy to produce a new language with a syntax based on SQL, which was superficially familiar, but there are many necessary differences at the lower levels. One issue where bullet biting is needed is nulls and three-valued logic; another is duplicate rows and

[sqlite] Mozilla wiki 'avoid SQLite'

> On Jun 18, 2015, at 5:10 PM, Marc L. Allen > wrote: > > Frankly, I've avoided taking a close look at Andl because of its massive use > of special characters. I can usually work out a rough meaning on your > examples because I know the SQL it came from. If I became 'Andl proficient' > it

[sqlite] Mozilla wiki 'avoid SQLite'

Simon Slavin wrote: > The thing I always found interesting about SQL was that it picks three > English words, INSERT, DELETE, UPDATE, and says that that's all you need to > do. And it's right ! Is there something special about the 'three-ness' of > database operations ? Or are you meant to

[sqlite] Mozilla wiki 'avoid SQLite'

On Wed, 17 Jun 2015 22:05:12 -0700 Darren Duncan wrote: > I also believe the world is ripe to have SQL alternatives, its just > a matter of ones appearing that are compelling to users for real work > and not just an academic exercise. The fact we're still generally > with SQL means this hasn't

[sqlite] Mozilla wiki 'avoid SQLite'

Thanks for your response, James, and I agree with what you've said. My own language family, Muldis D, takes all of those things into account. For examples of this: 1. Muldis D is a general purpose language like for applications but it also is fundamentally savvy to the needs and features of

[sqlite] Mozilla wiki 'avoid SQLite'

I don't have enough experience in any FP language to be productive. C# has a lot of FP like features (lambdas, LINQ, etc) that I do know how to use. And ultimately, the C# version could be recoded in C++ if it's worth doing. The question for now is: does a new database programming language have a

[sqlite] Mozilla wiki 'avoid SQLite'

I should also clarify that I don't see SQL as *a* language but rather as a family of languages. Each actual SQL language in the family is whatever some particular SQL DBMS actually implements and how it behaves. So eg "SQLite SQL" is *a* SQL language, with generally a distinct version for

[sqlite] Likelihood() in Left Join affecting results

On 2015-06-18 01:04 PM, Jean Chevalier wrote: > The likelihood() function, which should help select a query plan but > otherwise be logic-neutral, nevertheless seems to affect results returned by > a Left Join, when used as part of the join condition, possibly in other > circumstances. To

[sqlite] Mozilla wiki 'avoid SQLite'

On 2015-06-18 3:35 AM, ajm at zator.com wrote: > Darren: > > Maybe you're right. But to that relationship of "goodness" that would be > desirable, perhaps we should add a few drops of pragmatism. Experience shows > that in many cases, the perfect is the enemy of the good, and despite a >

[sqlite] Likelihood() in Left Join affecting results

The likelihood() function, which should help select a query plan but otherwise be logic-neutral, nevertheless seems to affect results returned by a Left Join, when used as part of the join condition, possibly in other circumstances. With the following sample data, the two SELECT queries should

[sqlite] SQLite PENDING lock before SHARED lock with WAL enabled

Thanks for your feedback. We can confirm that the database is in WAL mode. After some further digging, we have found out It only happens with the very first query. SQLite calls sqlite3InitOne when DbHasProperty(db, 1, DB_SchemaLoaded) is false. Apparently, the schema is loaded into memory via

[sqlite] Mozilla wiki 'avoid SQLite'

> Mensaje original > De: > Para: "'General Discussion of SQLite Database'" mailinglists.sqlite.org> > Fecha: Thu, 18 Jun 2015 14:50:40 +1000 > Asunto: Re: [sqlite] Mozilla wiki 'avoid SQLite' > Darren: Maybe you're right. But to that relationship of "goodness" that would be

[sqlite] SQLite (1.0.97) access via LAN

We are developing Windows applications with SQLite.dll. The current situation with VisualStudio-2010 is as follow: For x32 target compilation with System.Data.SQLite-x32-1.0.97.dll (.NET4) My application works fine. For x64 target compilation with System.Data.SQLite-x64-1.0.97.dll (.NET4)

[sqlite] What's the best way to pass function information to virtual table?

Thanks, MikeN. I will consider MATCH for now, although it is not standard. 2015-06-17 8:48 GMT-07:00 Mike Nicolino : > The override of match() trick works pretty well for cases like this. I've > overridden match in my virtual table implementation to allow me to pass > arbitrary specialized

[sqlite] What's the best way to pass function information to virtual table?

Thanks, Clemens. Some of my comments as follows 2015-06-17 1:23 GMT-07:00 Clemens Ladisch : > Jerry wrote: > > With xBestIndex and xFilter, we can pass the constraint information > (e.g., > > those from WHERE clause) to virtual table (through struct > > sqlite3_index_info), so that we can locate

[sqlite] Likelihood() in Left Join affecting results

Thanks for the bug report. The problem is now fixed on trunk. On 6/18/15, Jean Chevalier wrote: > The likelihood() function, which should help select a query plan but > otherwise be logic-neutral, nevertheless seems to affect results returned by > a Left Join, when used as part of the join

[sqlite] Mozilla wiki 'avoid SQLite'

Frankly, I've avoided taking a close look at Andl because of its massive use of special characters. I can usually work out a rough meaning on your examples because I know the SQL it came from. If I became 'Andl proficient' it probably wouldn't be a problem, but I gotta ask.. what's the issue

[sqlite] Mozilla wiki 'avoid SQLite'

Indeed, I'm agree with Darren, and continuing its thought, perhaps that hypothetical new language would be a clean extensi?n of SQL in the same way that C++ was respect to C, simplifying the transition and reutilization of legacy code. Cheers. -- A.J. Millan > > Mensaje original >

[sqlite] Mozilla wiki 'avoid SQLite'

I don't understand all the issues with SQL as it is today. I doubt I'm at the level of most of the posters in this group. However, I do write a mess of it so I thought I'd give my two cents as a programmer. For what it does, SQL does it really well. That is, it takes a couple of sets of

[sqlite] SQLite PENDING lock before SHARED lock with WAL enabled

A SELECT query obtains a SHARED lock on the database file. Doing so, there can be many simultaneous readers according to the documentation at https://www.sqlite.org/lockingv3.html. However, before the SHARED lock is obtained in winLock(sqlite3_file *id, int locktype), a temporary PENDING lock

[sqlite] SQLite PENDING lock before SHARED lock with WAL enabled

On 6/18/15, Harmen de Jong - CoachR Group B.V. wrote: > A SELECT query obtains a SHARED lock on the database file. Doing so, there > can be many simultaneous readers according to the documentation at > https://www.sqlite.org/lockingv3.html. However, before the SHARED lock is > obtained in

[sqlite] Mozilla wiki 'avoid SQLite'

I disagree with the idea that a good SQL alternative would just be a superset of SQL as you propose. That has already been done numerous times, the principal manifestations being each SQL DBMS that has its own small or large differences in syntax and features from each other. SQL is already