Re: [sqlite] AUTOINCREMENT documentation.

2009-02-18 Thread Marcin Walkowiak - Work (local #2)

> 
> Not exactly,
> in monotonically increasing sequence next element is always smaller than
> current.
> 

I mean larger :-)

Sorry,
KoD

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


Re: [sqlite] AUTOINCREMENT documentation.

2009-02-18 Thread Marcin Walkowiak - Work (local #2)
Troeger, Thomas (ext) wrote:
> Hello,
> 
> Sorry if this has been asked before, I couldn't find any reference to it
> in the list archives. I've found a small bug in the documentation, I
> wanted to mention it since I think it should be changed accordingly.
> 
> In http://www.sqlite.org/autoinc.html the documentation says:
> 
> """
> The normal ROWID selection algorithm described above will generate
> monotonically increasing unique ROWIDs ...
> ...
> The AUTOINCREMENT Keyword
> ...
> Note that "monotonically increasing" does not imply that the ROWID
> always increases by exactly one. One is the usual increment. ...
> """
> 
> AFAIK, in a monotonically increasing sequence a value is larger *or
> equal* to the previous value, while in a *strictly* monotonically
> increasing sequence the next value is always larger (see
> http://en.wikipedia.org/wiki/Monotonic_function). This is maybe
> nitpicking, but I think the documentation should be fixed.
> 
> Regards,
> T.
> 
> P.S.: I hope this is the right place to ask such things, I couldn't find
> any documentation improvement link, else I would comment on some
> spelling errors as well ;-)
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
> 

Not exactly,
in monotonically increasing sequence next element is always smaller than
current.

Sequence where consecutive elements can be equal is called monotonically
nondecreasing sequence.

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


Re: [sqlite] OLE DB provider for SQLite

2008-11-17 Thread Marcin Walkowiak
-Original Message-
Date: Mon, 17 Nov 2008 08:53:44 -0500
From: "Brad Stiles" <[EMAIL PROTECTED]>
Subject: Re: [sqlite] OLE DB provider for SQLite
To: "General Discussion of SQLite Database" 
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1

>> PS Managed (ADO.NET) providers do not satisfy requirements for
>> performance reasons.

> That's a pretty blanket statement.  I've found Robert Simpson's
> ADO.NET provider to be very performant.  He has a benchmarking suite
> he wrote to compare various DBs.  It might still be available for
> download.

The problem with performance is not caused directly by SQLite provider, but by 
different way of reading data from managed (ADO.NET) providers by Analysis 
Services.

I know managed SQLite providers (like System.Data.SQLite) well, and I know that 
they are fast. I've tested performance of them. But in this case the difference 
between OLE DB providers and ADO.NET providers is great. For example when we 
underline MSSQL provider for SSAS:

ADO.NET (System.Data.SQLClient): 114 sec
OLE DB (SQLNCLI.1): 23 sec

This performance problem IS NOT restricted to SQLite provider, it occurs in all 
ADO.NET providers I've tested.

KoD


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


[sqlite] OLE DB provider for SQLite

2008-11-17 Thread Marcin Walkowiak (Work-Local Account)
Is there any OLE DB provider for SQLite other than provider from Cherry 
City Software:

http://cherrycitysoftware.com/ccs/Providers/ProvSQLite.aspx

Unfortunately this provider does not work well with one of my company's 
project (it must with Analysis Services and OLAP).

Could You tell me, are there another OLE DB providers?


PS Managed (ADO.NET) providers do not satisfy requirements for 
performance reasons.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users