date:20130411

Re: [sqlite] correlated subquery in LIMIT/OFFSET?

2013-04-11 Thread James K. Lowden

On Thu, 11 Apr 2013 17:14:43 +0200
Clemens Ladisch  wrote:

> >> It should come (or be derived) from the current row in the outer
> >> query.
> >
> > Sorry, but inner queries are performed first.
> 
> Sorry, but *correlated* inner queries are performed once for each
> record in the outer query.

*Logically* performed, you mean.  It's helpful to think of correlated
subqueries as being performed once per row.  It's also helpful to
remember there is no "before" or "after" while a query is executing.
The DBMS is free to execute your query in whatever fashion it chooses.  

Your query is incorrectly construed, however, 

select (select 42 limit 1 offset (select t.x)) from t;

assumes IIUC an order to t that isn't there, and a count that can't, in
general, be known.  

The only way to compute a median is to sort and count the input first.
That can be done by joining the table to itself to get an ordinal, and
by testing that product against itself in an EXISTS clause.  

The other way is to write a UDF, which isn't too hard if you assume all
value can be represented as double-precision floating point.  

--jkl
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] ORDER BY finds "AS" names ambiguous that shouldn't be?

2013-04-11 Thread Perry Wagle


On Apr 11, 2013, at 5:56 AM, Stephen Chrzanowski  wrote:

> Looking at the query, in the CLI, what if you rename the three bolded
> "title" fields to something else?  I think the system is getting messed up
> because a field in a table is called "title" and you're naming a query
> called "title" but you're not distinctly stating which "title" you want to
> query against, as in a table field or your query.  Not to mention it looks
> like you're doing the SORT BY twice against the same field in the same
> manor.  Mind you I have NOT tested this against anything.

I already tried that, and it failed.  I didn't try harder because the second
occurrence of title is there because the generating code supplies it, it
seems to be pulling fields out by name, the string "title" occurs about 150
times in the code, and I don't know which to change.  It also seems to
indicate that I need to rename all the names external to the query, not
just "title".  I will need to experiment harder.

Thanks!

> 
> sqlite> SELECT (CASE bms.title ISNULL WHEN 1 THEN moz_places.url ELSE (CASE
> bms.title WHEN '' THEN moz_places.url ELSE bms.title END) END) AS * title*,
> (CASE moz_places.favicon_id ISNULL WHEN 1 THEN '' ELSE (SELECT
> 'moz-anno:favicon:' || moz_favicons.url FROM moz_favicons WHERE
> moz_favicons.id = moz_places.favicon_id) END) AS favicon, moz_places.url AS
> url, moz_places.visit_count AS visit_count, moz_places.frecency AS
> frecency, bms.id AS id, bms.dateAdded AS dateAdded, bms.lastModified AS
> lastModified, (SELECT max(visit_date) FROM moz_historyvisits WHERE place_id
> = moz_places.id) AS visit_date FROM (SELECT fk AS id FROM moz_bookmarks
> WHERE parent IN (6068538) GROUP BY fk HAVING count(*) = 1) AS t,
> moz_places, moz_bookmarks AS folders, moz_bookmarks AS bms WHERE t.id =
> moz_places.id AND t.id = bms.fk AND bms.parent = folders.id AND
> folders.parent != 4 GROUP BY bms.id ORDER BY *title *COLLATE NOCASE ASC, 
> *title
> *COLLATE NOCASE ASC;
> 
> 
> 
> 
> On Wed, Apr 10, 2013 at 3:32 PM, Perry Wagle  wrote:
> 
>> 
>> On Apr 10, 2013, at 5:33 AM, Richard Hipp  wrote:
>> 
>>> On Wed, Apr 10, 2013 at 4:39 AM, Perry Wagle  wrote:
>>> 
 I have a problem with a field name being ambiguous when it wasn't
>> before.
 Is this a bug or a feature?
 
 Firefox 19 uses Sqlite 3.7.14.1 which does what it should.  Firefox 20
 uses Sqlite 3.7.15.2 which complains that "title" is ambiguous in the
>> ORDER
 BY in the below query:
 
 SELECT (CASE bms.title ISNULL WHEN 1 THEN moz_places.url ELSE (CASE
 bms.title WHEN '' THEN moz_places.url ELSE bms.title END) END) AS title,
 (CASE moz_places.favicon_id ISNULL WHEN 1 THEN '' ELSE (SELECT
 'moz-anno:favicon:' || moz_favicons.url FROM moz_favicons WHERE
 moz_favicons.id = moz_places.favicon_id) END) AS favicon,
>> moz_places.url
 AS url, moz_places.visit_count AS visit_count, moz_places.frecency AS
 frecency, bms.id AS id, bms.dateAdded AS dateAdded, bms.lastModified AS
 lastModified, (SELECT max(visit_date) FROM moz_historyvisits WHERE
>> place_id
 = moz_places.id) AS visit_date FROM (SELECT fk AS id FROM moz_bookmarks
 WHERE parent IN (6068538) GROUP BY fk HAVING count(*) = 1) AS t,
 moz_places, moz_bookmarks AS folders, moz_bookmarks AS bms WHERE t.id =
 moz_places.id AND t.id = bms.fk AND bms.parent = folders.id AND
 folders.parent != 4 GROUP BY bms.id ORDER BY title COLLATE NOCASE ASC,
 title COLLATE NOCASE ASC
 
 I claim "title" shouldn't be ambiguous, since the first SELECT
>> expression
 was named "title".  What's the consensus?
 
>>> 
>>> There were enhancements to name resolution in 3.7.16.  Did you try it
>>> there?
>> 
>> See below:
>> 
>> SQLite version 3.7.16.1 2013-03-29 13:44:34
>> Enter ".help" for instructions
>> Enter SQL statements terminated with a ";"
>> sqlite> SELECT (CASE bms.title ISNULL WHEN 1 THEN moz_places.url ELSE
>> (CASE bms.title WHEN '' THEN moz_places.url ELSE bms.title END) END) AS
>> title, (CASE moz_places.favicon_id ISNULL WHEN 1 THEN '' ELSE (SELECT
>> 'moz-anno:favicon:' || moz_favicons.url FROM moz_favicons WHERE
>> moz_favicons.id = moz_places.favicon_id) END) AS favicon, moz_places.url
>> AS url, moz_places.visit_count AS visit_count, moz_places.frecency AS
>> frecency, bms.id AS id, bms.dateAdded AS dateAdded, bms.lastModified AS
>> lastModified, (SELECT max(visit_date) FROM moz_historyvisits WHERE place_id
>> = moz_places.id) AS visit_date FROM (SELECT fk AS id FROM moz_bookmarks
>> WHERE parent IN (6068538) GROUP BY fk HAVING count(*) = 1) AS t,
>> moz_places, moz_bookmarks AS folders, moz_bookmarks AS bms WHERE t.id =
>> moz_places.id AND t.id = bms.fk AND bms.parent = folders.id AND
>> folders.parent != 4 GROUP BY bms.id ORDER BY title COLLATE NOCASE ASC,
>> title COLLATE NOCASE ASC;
>> Error: ambiguous column name: title
>> 
>>> 
>>> --
>>> D. Richard Hipp
>>>

Re: [sqlite] correlated subquery in LIMIT/OFFSET?

2013-04-11 Thread Clemens Ladisch

Simon Slavin wrote:
> On 11 Apr 2013, at 2:38pm, Clemens Ladisch  wrote:
>>>  sqlite> create table t(x);
>>>  sqlite> select (select 42 limit 1 offset (select t.x)) from t;
>>>  Error: no such column: t.x
>
>> It should come (or be derived) from the current row in the outer query.
>
> Sorry, but inner queries are performed first.

Sorry, but *correlated* inner queries are performed once for each record
in the outer query.

To take your ballsy example: with the following data:

  create table balls(
color varchar(10),
size integer
  );
  insert into balls values('blue', 1);
  insert into balls values('blue', 2);
  insert into balls values('red', 3);
  insert into balls values('red', 44);
  insert into balls values('red', 555);

this query works just fine:

  select color,
 (select avg(size) from balls where color = b.color)
  from (select distinct color from balls) b;

(This could be done much easier with GROUP BY; I'm just demonstrating
how correlated subqueries work.)

> Your original post said "for computing the median of a group".

With PostgreSQL, this works ():

  select color,
 (select size
  from balls
  where color = b.color
  order by size
  limit 1
  offset (select cast(count(*) / 2 as integer)
  from balls
  where color = b.color)
 ) as median
  from (select distinct color from balls) b;

> The fastest way to do that without creating a SQLite extension ...

Thanks for the workaround, but I'm asking if there is any good reason
why SQLite does not support this.  As far as I can tell, (scalar)
correlated subqueries work in every other context.


Regards,
Clemens
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] correlated subquery in LIMIT/OFFSET?

2013-04-11 Thread Simon Slavin

On 11 Apr 2013, at 2:38pm, Clemens Ladisch  wrote:

>>  sqlite> create table t(x);
>>  sqlite> select (select 42 limit 1 offset (select t.x)) from t;
>>  Error: no such column: t.x

> It should come (or be derived) from the current row in the outer query.

Sorry, but inner queries are performed first.  The outer query is analysed for 
parameters, but rows have not been fetched at the time inner queries are 
executed.

Your original post said "for computing the median of a group".  The fastest way 
to do that without creating a SQLite extension for it is to first count the 
number of items in the group then do a SELECT.  Unforunately it's going to be 
faster to do this in your programming language than it is to try to make one 
convoluted SQL statement to do it all.  The counting SELECT would be something 
like

SELECT count(*) FROM myTable WHERE theGroup="redballs"

Unfortunately this may give an odd or even result, and the OFFSET parameter 
must evaluate to an integer, so you cant just halve it, you have to do a little 
maths or a little 'if'.  The median entry would then be the expected

SELECT ballSize FROM myTable WHERE theGroup="redballs" ORDER BY ballSize OFFSET 
[value stored earlier] LIMIT 1

A neater solution would be to define your own aggregate function which finds 
the median of all the values fed to it.  Then you could just do

SELECT myMedian(ballSize) FROM myTable WHERE theGroup="redballs"

Simon.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] correlated subquery in LIMIT/OFFSET?

2013-04-11 Thread Michael Black

I think you need a more complete example with the output you expect to get
better help.  Although I do understand what you're getting at.

Mike

-Original Message-
From: sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Clemens Ladisch
Sent: Thursday, April 11, 2013 8:39 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] correlated subquery in LIMIT/OFFSET?

Michael Black wrote:
> > However, it appears that SQLite does not allow correlated subqueries
> > in the LIMIT/OFFSET clauses of a scalar subquery:
> >
> >   sqlite> create table t(x);
> >   sqlite> select (select 42 limit 1 offset (select t.x)) from t;
> >   Error: no such column: t.x
>
> Instead of "select t.x" don't you really want "select x from t" ??

No, I want it to be a *correlated* subquery.

> I assume you just want the offset to come from a single-row table?

It should come (or be derived) from the current row in the outer query.


Regards,
Clemens
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] correlated subquery in LIMIT/OFFSET?

2013-04-11 Thread Clemens Ladisch

Michael Black wrote:
> > However, it appears that SQLite does not allow correlated subqueries
> > in the LIMIT/OFFSET clauses of a scalar subquery:
> >
> >   sqlite> create table t(x);
> >   sqlite> select (select 42 limit 1 offset (select t.x)) from t;
> >   Error: no such column: t.x
>
> Instead of "select t.x" don't you really want "select x from t" ??

No, I want it to be a *correlated* subquery.

> I assume you just want the offset to come from a single-row table?

It should come (or be derived) from the current row in the outer query.


Regards,
Clemens
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] correlated subquery in LIMIT/OFFSET?

2013-04-11 Thread Michael Black

Instead of "select t.x" don't you really want "select x from t" ??

That seems to work at least syntactically.  I assume you just want the
offset to come from a single-row table?
Mike


-Original Message-
From: sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Clemens Ladisch
Sent: Thursday, April 11, 2013 8:15 AM
To: sqlite-users@sqlite.org
Subject: [sqlite] correlated subquery in LIMIT/OFFSET?

Hi,

for computing the median of a group, it would be useful to be able to
use a correlated subquery as the expression in a OFFSET clause.

However, it appears that SQLite does not allow correlated subqueries
in the LIMIT/OFFSET clauses of a scalar subquery:

  sqlite> create table t(x);
  sqlite> select (select 42 limit 1 offset (select t.x)) from t;
  Error: no such column: t.x

Is this behaviour by design?

The documentation says that the LIMIT clause of a scalar subquery is
ignored and gets replaced with 1, but this shouldn't disallow the syntax
above, and should not apply to the OFFSET value in any case.


Regards,
Clemens
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] correlated subquery in LIMIT/OFFSET?

2013-04-11 Thread Clemens Ladisch

Hi,

for computing the median of a group, it would be useful to be able to
use a correlated subquery as the expression in a OFFSET clause.

However, it appears that SQLite does not allow correlated subqueries
in the LIMIT/OFFSET clauses of a scalar subquery:

  sqlite> create table t(x);
  sqlite> select (select 42 limit 1 offset (select t.x)) from t;
  Error: no such column: t.x

Is this behaviour by design?

The documentation says that the LIMIT clause of a scalar subquery is
ignored and gets replaced with 1, but this shouldn't disallow the syntax
above, and should not apply to the OFFSET value in any case.


Regards,
Clemens
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] ORDER BY finds "AS" names ambiguous that shouldn't be?

2013-04-11 Thread Stephen Chrzanowski

Looking at the query, in the CLI, what if you rename the three bolded
"title" fields to something else?  I think the system is getting messed up
because a field in a table is called "title" and you're naming a query
called "title" but you're not distinctly stating which "title" you want to
query against, as in a table field or your query.  Not to mention it looks
like you're doing the SORT BY twice against the same field in the same
manor.  Mind you I have NOT tested this against anything.

sqlite> SELECT (CASE bms.title ISNULL WHEN 1 THEN moz_places.url ELSE (CASE
bms.title WHEN '' THEN moz_places.url ELSE bms.title END) END) AS * title*,
(CASE moz_places.favicon_id ISNULL WHEN 1 THEN '' ELSE (SELECT
'moz-anno:favicon:' || moz_favicons.url FROM moz_favicons WHERE
moz_favicons.id = moz_places.favicon_id) END) AS favicon, moz_places.url AS
url, moz_places.visit_count AS visit_count, moz_places.frecency AS
frecency, bms.id AS id, bms.dateAdded AS dateAdded, bms.lastModified AS
lastModified, (SELECT max(visit_date) FROM moz_historyvisits WHERE place_id
= moz_places.id) AS visit_date FROM (SELECT fk AS id FROM moz_bookmarks
WHERE parent IN (6068538) GROUP BY fk HAVING count(*) = 1) AS t,
moz_places, moz_bookmarks AS folders, moz_bookmarks AS bms WHERE t.id =
moz_places.id AND t.id = bms.fk AND bms.parent = folders.id AND
folders.parent != 4 GROUP BY bms.id ORDER BY *title *COLLATE NOCASE ASC, *title
*COLLATE NOCASE ASC;




On Wed, Apr 10, 2013 at 3:32 PM, Perry Wagle  wrote:

>
> On Apr 10, 2013, at 5:33 AM, Richard Hipp  wrote:
>
> > On Wed, Apr 10, 2013 at 4:39 AM, Perry Wagle  wrote:
> >
> >> I have a problem with a field name being ambiguous when it wasn't
> before.
> >> Is this a bug or a feature?
> >>
> >> Firefox 19 uses Sqlite 3.7.14.1 which does what it should.  Firefox 20
> >> uses Sqlite 3.7.15.2 which complains that "title" is ambiguous in the
> ORDER
> >> BY in the below query:
> >>
> >> SELECT (CASE bms.title ISNULL WHEN 1 THEN moz_places.url ELSE (CASE
> >> bms.title WHEN '' THEN moz_places.url ELSE bms.title END) END) AS title,
> >> (CASE moz_places.favicon_id ISNULL WHEN 1 THEN '' ELSE (SELECT
> >> 'moz-anno:favicon:' || moz_favicons.url FROM moz_favicons WHERE
> >> moz_favicons.id = moz_places.favicon_id) END) AS favicon,
> moz_places.url
> >> AS url, moz_places.visit_count AS visit_count, moz_places.frecency AS
> >> frecency, bms.id AS id, bms.dateAdded AS dateAdded, bms.lastModified AS
> >> lastModified, (SELECT max(visit_date) FROM moz_historyvisits WHERE
> place_id
> >> = moz_places.id) AS visit_date FROM (SELECT fk AS id FROM moz_bookmarks
> >> WHERE parent IN (6068538) GROUP BY fk HAVING count(*) = 1) AS t,
> >> moz_places, moz_bookmarks AS folders, moz_bookmarks AS bms WHERE t.id =
> >> moz_places.id AND t.id = bms.fk AND bms.parent = folders.id AND
> >> folders.parent != 4 GROUP BY bms.id ORDER BY title COLLATE NOCASE ASC,
> >> title COLLATE NOCASE ASC
> >>
> >> I claim "title" shouldn't be ambiguous, since the first SELECT
> expression
> >> was named "title".  What's the consensus?
> >>
> >
> > There were enhancements to name resolution in 3.7.16.  Did you try it
> > there?
>
> See below:
>
> SQLite version 3.7.16.1 2013-03-29 13:44:34
> Enter ".help" for instructions
> Enter SQL statements terminated with a ";"
> sqlite> SELECT (CASE bms.title ISNULL WHEN 1 THEN moz_places.url ELSE
> (CASE bms.title WHEN '' THEN moz_places.url ELSE bms.title END) END) AS
> title, (CASE moz_places.favicon_id ISNULL WHEN 1 THEN '' ELSE (SELECT
> 'moz-anno:favicon:' || moz_favicons.url FROM moz_favicons WHERE
> moz_favicons.id = moz_places.favicon_id) END) AS favicon, moz_places.url
> AS url, moz_places.visit_count AS visit_count, moz_places.frecency AS
> frecency, bms.id AS id, bms.dateAdded AS dateAdded, bms.lastModified AS
> lastModified, (SELECT max(visit_date) FROM moz_historyvisits WHERE place_id
> = moz_places.id) AS visit_date FROM (SELECT fk AS id FROM moz_bookmarks
> WHERE parent IN (6068538) GROUP BY fk HAVING count(*) = 1) AS t,
> moz_places, moz_bookmarks AS folders, moz_bookmarks AS bms WHERE t.id =
> moz_places.id AND t.id = bms.fk AND bms.parent = folders.id AND
> folders.parent != 4 GROUP BY bms.id ORDER BY title COLLATE NOCASE ASC,
> title COLLATE NOCASE ASC;
> Error: ambiguous column name: title
>
> >
> > --
> > D. Richard Hipp
> > d...@sqlite.org
> > ___
> > sqlite-users mailing list
> > sqlite-users@sqlite.org
> > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] FreeBSD and SQLITE_ENABLE_LOCKING_STYLE

2013-04-11 Thread Richard Hipp

On Thu, Apr 11, 2013 at 4:03 AM, Baptiste Daroussin <
baptiste.darous...@gmail.com> wrote:

> Ok so I was not going in the right direction :)
>
> So how it is possible to corrupt a database on nfsv4? Does that ring a bell
> to someone?
>
>
Probably the posix advisory locks are not working.  Have you tried running
using the "unix-dotfile" VFS?



>
>
>
> 2013/4/11 Richard Hipp 
>
> > On Wed, Apr 10, 2013 at 6:40 PM, Baptiste Daroussin <
> > baptiste.darous...@gmail.com> wrote:
> >
> > > I'm trying to activate SQLITE_ENABLE_LOCKING_STYLE=1 on FreeBSD.
> > >
> >
> > The SQLITE_ENABLE_LOCKING_STYLE compile-time option is code that was
> > contributed and supported by Apple specifically for use on Mac OS-X.
> > Unfortunately, the engineer at Apple who was providing that support has
> > moved on and so the SQLITE_ENABLE_LOCKING_STYLE compile-time option has
> > been orphaned.  It is currently unsupported and untested.
> >
> > Note that the SQLite core team contains to support, maintain, and test
> > SQLite on OS-X.  We just don't provide support for the
> > SQLITE_ENABLE_LOCKING_STYLE compile-time option.
> >
> > --
> > D. Richard Hipp
> > d...@sqlite.org
> > ___
> > sqlite-users mailing list
> > sqlite-users@sqlite.org
> > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
> >
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>



-- 
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] FreeBSD and SQLITE_ENABLE_LOCKING_STYLE

2013-04-11 Thread Simon Davies

On 11 April 2013 09:03, Baptiste Daroussin  wrote:
> Ok so I was not going in the right direction :)
>
> So how it is possible to corrupt a database on nfsv4? Does that ring a bell
> to someone?

In case you have not already seen it:
http://www.sqlite.org/lockingv3.html#how_to_corrupt

Regards,
Simon
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] FreeBSD and SQLITE_ENABLE_LOCKING_STYLE

2013-04-11 Thread Baptiste Daroussin

Ok so I was not going in the right direction :)

So how it is possible to corrupt a database on nfsv4? Does that ring a bell
to someone?




2013/4/11 Richard Hipp 

> On Wed, Apr 10, 2013 at 6:40 PM, Baptiste Daroussin <
> baptiste.darous...@gmail.com> wrote:
>
> > I'm trying to activate SQLITE_ENABLE_LOCKING_STYLE=1 on FreeBSD.
> >
>
> The SQLITE_ENABLE_LOCKING_STYLE compile-time option is code that was
> contributed and supported by Apple specifically for use on Mac OS-X.
> Unfortunately, the engineer at Apple who was providing that support has
> moved on and so the SQLITE_ENABLE_LOCKING_STYLE compile-time option has
> been orphaned.  It is currently unsupported and untested.
>
> Note that the SQLite core team contains to support, maintain, and test
> SQLite on OS-X.  We just don't provide support for the
> SQLITE_ENABLE_LOCKING_STYLE compile-time option.
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] System.Data.Sqlite NuGet

2013-04-11 Thread Joe Mistachkin

Baruch Burstein wrote:
>
> I installed System.Data.Sqlite from via NuGet, but I don't see it in the
> options for creating a new database (server explorer or whatever it is
> called). I am using VS2010 Ultimate.
> Am I doing something wrong?
> 

The NuGet packages for System.Data.SQLite do not include the design-time
components for Visual Studio.  If you require these components, one of the
following setup packages should also be used:

Visual Studio 2005: sqlite-netFx20-setup-bundle-x86-2005-1.0.84.0.exe
Visual Studio 2008: sqlite-netFx35-setup-bundle-x86-2008-1.0.84.0.exe
Visual Studio 2010: sqlite-netFx40-setup-bundle-x86-2010-1.0.84.0.exe
Visual Studio 2012: sqlite-netFx45-setup-bundle-x86-2012-1.0.84.0.exe

The above files may be downloaded from the System.Data.SQLite download
page, here:

https://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki

In the future, you should be able to obtain the latest version of these
setup packages by simply replacing "1.0.84.0" with the latest release
version number.

It should also be noted that installing one of the above packages will
install the core System.Data.SQLite assemblies into the Global Assembly
Cache and this may not always be desirable.  Unfortunately, this is a
requirement that Visual Studio appears to impose on managed assemblies
referenced by an installed package.

--
Joe Mistachkin

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] System.Data.Sqlite NuGet

2013-04-11 Thread Baruch Burstein

I installed System.Data.Sqlite from via NuGet, but I don't see it in the
options for creating a new database (server explorer or whatever it is
called). I am using VS2010 Ultimate.
Am I doing something wrong?

-- 
˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] correlated subquery in LIMIT/OFFSET?

Re: [sqlite] ORDER BY finds "AS" names ambiguous that shouldn't be?

Re: [sqlite] correlated subquery in LIMIT/OFFSET?

Re: [sqlite] correlated subquery in LIMIT/OFFSET?

Re: [sqlite] correlated subquery in LIMIT/OFFSET?

Re: [sqlite] correlated subquery in LIMIT/OFFSET?

Re: [sqlite] correlated subquery in LIMIT/OFFSET?

[sqlite] correlated subquery in LIMIT/OFFSET?

Re: [sqlite] ORDER BY finds "AS" names ambiguous that shouldn't be?

Re: [sqlite] FreeBSD and SQLITE_ENABLE_LOCKING_STYLE

Re: [sqlite] FreeBSD and SQLITE_ENABLE_LOCKING_STYLE

Re: [sqlite] FreeBSD and SQLITE_ENABLE_LOCKING_STYLE

Re: [sqlite] System.Data.Sqlite NuGet

[sqlite] System.Data.Sqlite NuGet

14 matches

Site Navigation

Mail list logo

Footer information