Re: [sqlite] Most wanted features of SQLite ?

P Kishor wrote: > On Sat, Sep 19, 2009 at 9:21 AM, John Stanton wrote: >> Alexey Pechnikov wrote: >>> Hello! >>> >>> On Saturday 19 September 2009 00:43:18 Noah Hart wrote: >>> Stored Procedures >>> There are Tiny C compiler extension and realization of >>> stored

Re: [sqlite] Most wanted features of SQLite ?

Alexey Pechnikov wrote: > Hello! > > On Saturday 19 September 2009 18:21:22 John Stanton wrote: >> There is a PL/SQL implementation available and we use Javascript as a >> stored procedure capability in Sqlite. It integrates nicely with WWW >> applications. > > I don't know this. Can you show

Re: [sqlite] Most wanted features of SQLite?: Stored procedures

On 20/09/2009, at 6:57 AM, Simon Slavin wrote: > > Ah. Okay, so in SQLite3 you can emulate stored procedures using > triggers. Just define a trigger to operate on something that > doesn't matter to you. For instance inserting a record in a table > that you never bother reading. Every so

Re: [sqlite] Most wanted features of SQLite?: Access to database structure

I would like to see some more access to the database structure via SQL calls. For instance, we can currently get the list of tables, views, indexes and/or triggers via queries to SQLite_Master. For instance, to get the name and SQL of all triggers that are initiated by MyTable, we can

Re: [sqlite] Most wanted features of SQLite ?

On 21 Sep 2009, at 9:36pm, Fred Williams wrote: > would SQLite not work as the "back end" > for a client server (wrapper) implementation that did the multi > process (or > whatever) lock management up one level so to speak? Great question. I don't know. It requires either in-depth

Re: [sqlite] Most wanted features of SQLite ?

Simon Slavin wrote: > >> I definitely don't agree here as we're talking about these additional >> locks existing _only_ in memory, not on disk. > > Which requires client/server architecture. Which SQLite3 doesn't > have. Once you require concurrent access features in your DBMS (i.e. >

Re: [sqlite] Most wanted features of SQLite ?

-Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org]on Behalf Of Simon Slavin Sent: Monday, September 21, 2009 3:05 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] Most wanted features of SQLite ? On 21 Sep 2009, at 6:53pm

Re: [sqlite] Most wanted features of SQLite ?

On 21 Sep 2009, at 6:53pm, Brad House wrote: > I definitely don't agree here as we're talking about these additional > locks existing _only_ in memory, not on disk. Which requires client/server architecture. Which SQLite3 doesn't have. Once you require concurrent access features in your DBMS

Re: [sqlite] Most wanted features of SQLite ?

oking for is a form of NATURAL JOIN just..more natural :) -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Igor Tandetnik Sent: Monday, September 21, 2009 3:25 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Most wanted featu

Re: [sqlite] Most wanted features of SQLite ?

Shaun Seckman (Firaxis) wrote: > * I really would like some SQL syntax sugar that will > automatically include rows referenced by foreign keys in a table. I > haven't seen any other SQL database do this as all expect you to > explicitly include the conditions and joins

Re: [sqlite] Most wanted features of SQLite ?

] Most wanted features of SQLite ? >> It could probably benefit a large number of integrations to >> have finer grained locking even if it could not be implemented for all >> integration types. > > It makes the system a great deal slower, since you need to keep > checking

Re: [sqlite] Most wanted features of SQLite ?

>> It could probably benefit a large number of integrations to >> have finer grained locking even if it could not be implemented for all >> integration types. > > It makes the system a great deal slower, since you need to keep > checking all the levels of lock you have implemented. For

Re: [sqlite] Most wanted features of SQLite ?

Interesting point, Simon. Are you saying that all developers of big database engines that implemented row-level locks are just idiots because there's no benefit from it at all? They had to implement just database-level locks and all users would be a lot happier because they'd received a

Re: [sqlite] Most wanted features of SQLite ?

On 21 Sep 2009, at 5:38pm, Brad House wrote: > It could probably benefit a large number of integrations to > have finer grained locking even if it could not be implemented for all > integration types. It makes the system a great deal slower, since you need to keep checking all the levels of

Re: [sqlite] Most wanted features of SQLite ?

>> Fine for me. It seems to be everybody else that wants their favorite >> feature imbedded in the core :-) >> >> Fine grained locking would be a great "asset" I feel. Notice I did >> not >> request a "feature." > > > On my to-do list is to write a paper that explains why fine-grain >

Re: [sqlite] Most wanted features of SQLite ?

n of SQLite Database Subject: Re: [sqlite] Most wanted features of SQLite ? On Sep 21, 2009, at 8:58 AM, Fred Williams wrote: > > Fine for me. It seems to be everybody else that wants their favorite > feature imbedded in the core :-) > > Fine grained locking would be a

Re: [sqlite] Most wanted features of SQLite ?

On Sep 21, 2009, at 8:58 AM, Fred Williams wrote: > > Fine for me. It seems to be everybody else that wants their favorite > feature imbedded in the core :-) > > Fine grained locking would be a great "asset" I feel. Notice I did > not > request a "feature." On my to-do list is to write a

Re: [sqlite] Most wanted features of SQLite ?

to:sqlite-users-boun...@sqlite.org]on Behalf Of Alexey Pechnikov Sent: Monday, September 21, 2009 1:54 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] Most wanted features of SQLite ? Hello! On Monday 21 September 2009 01:45:07 Fred Williams wrote: > With the background of th

Re: [sqlite] Most wanted features of SQLite ?

Hello! On Monday 21 September 2009 14:33:30 Grzegorz Wierzchowski wrote: > BTW while we are at subject of SQLite extensions. > I'm very new on this e-mail list but already saw here and there in mails > several links to places around the web with some extensions. There are a lot of extensions in

Re: [sqlite] Most wanted features of SQLite ?

To: General Discussion of SQLite Database Subject: Re: [sqlite] Most wanted features of SQLite ? BTW while we are at subject of SQLite extensions. I'm very new on this e-mail list but already saw here and there in mails several links to places around the web with some extensions. What would you say

Re: [sqlite] Most wanted features of SQLite ?

BTW while we are at subject of SQLite extensions. I'm very new on this e-mail list but already saw here and there in mails several links to places around the web with some extensions. What would you say guys for creating some centalized list of (known/recommended ...) extensions somewhere on

Re: [sqlite] Most wanted features of SQLite ?

Hello! On Monday 21 September 2009 11:36:15 Roger Binns wrote: > Also not mentioned is that it is available under a public domain license and > hence anyone has the right to use it in any way they deem fit, make changes, > distribute changes, charge anything they want, keep everything public, >

Re: [sqlite] Most wanted features of SQLite ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexey Pechnikov wrote: > SQLite does have the best extensibility of known to me DBMS. Also not mentioned is that it is available under a public domain license and hence anyone has the right to use it in any way they deem fit, make changes,

Re: [sqlite] Most wanted features of SQLite ?

Hello! On Monday 21 September 2009 01:45:07 Fred Williams wrote: > With the background of the never ending drumbeat of "feature, feature, > feature..." on this list as a reason, I wonder if the structure of > SQLite could be "enhanced" to better support the "plug-in" concept, aka: > as with

Re: [sqlite] Most wanted features of SQLite ?

te.org]on Behalf Of sub sk79 Sent: Sunday, September 20, 2009 9:16 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] Most wanted features of SQLite ? ... ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Most wanted features of SQLite ?

StepSqlite PL/SQL compiler for SQLite is certainly not for all. It is simply aimed at what we believe is a majority. http://www.metatranz.com/stepsqlite/ regards, -sk >>But I write stored procedures and triggers for PostgreSQL on Tcl. PL/pgSQL or >>PL/SQL is not the best solution to all.

Re: [sqlite] Most wanted features of SQLite ?

-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Alexey Pechnikov Sent: Sunday, September 20, 2009 7:34 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] Most wanted features of SQLite ? Hello! On Sunday 20 September 2009 18:16:19 sub sk79 wrote: > PL/

Re: [sqlite] Most wanted features of SQLite ?

of things, never had to use ICU myself. Itamar. -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Simon Slavin Sent: Saturday, September 19, 2009 6:44 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] Most wanted

Re: [sqlite] Most wanted features of SQLite ?

Hello! On Sunday 20 September 2009 18:16:19 sub sk79 wrote: > PL/SQL has a very wide user-base and a huge repository of existing > code-base in the world. Using StepSqlite PL/SQL compiler this huge > base can use SQLite by reusing their code as well as reusing their > skills - no learning curve

Re: [sqlite] Most wanted features of SQLite ?

ite.org]on Behalf Of sub sk79 Sent: Sunday, September 20, 2009 9:16 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] Most wanted features of SQLite ? >> 1. Generate a loadable SQLite extension and distribute it with DB. > > We can write C extension without any wrapper. Why w

Re: [sqlite] Most wanted features of SQLite ?

Guillermo Varona Silupú wrote: > I want to insert this text: > > 1' equivale a 12" > > cQry := "INSERT INTO Tabla1 (Code,Equiv) VALUES (10, "1' equivale a > 12"") What language is that? ':=' suggests Pascal, but string literals in Pascal use single quotes. In SQL, string literals are surrounded

Re: [sqlite] Most wanted features of SQLite ?

>> 1. Generate a loadable SQLite extension and distribute it with DB. > > We can write C extension without any wrapper. Why we need to learn > your extension for getting the same result and possible new bugs? PL/SQL has a very wide user-base and a huge repository of existing code-base in the

Re: [sqlite] Most wanted features of SQLite ?

Hi I want to insert this text: 1' equivale a 12" cQry := "INSERT INTO Tabla1 (Code,Equiv) VALUES (10, "1' equivale a 12"") TIA Best Regards GVS ___ sqlite-users mailing list sqlite-users@sqlite.org

Re: [sqlite] Most wanted features of SQLite ?

Hello! On Sunday 20 September 2009 08:05:04 Darren Duncan wrote: > The more general solution here to the duplicate column name problem is to be > stricter than the SQL standard and treat attempts to return duplicate column > names as a syntax or constraint error. For example, if you had 2

Re: [sqlite] Most wanted features of SQLite ?

Hello! On Sunday 20 September 2009 02:42:30 Darren Duncan wrote: > As for Tcl, well one solution there is to create a new singleton TCL type and > use its one value to correspond to NULL, and so then empty string will > continue > to just mean empty string, as it should. Not being able to

Re: [sqlite] Most wanted features of SQLite ?

Hello! On Sunday 20 September 2009 02:45:32 sub sk79 wrote: > 1. Generate a loadable SQLite extension and distribute it with DB. We can write C extension without any wrapper. Why we need to learn your extension for getting the same result and possible new bugs? > 2. If distributing loadable

Re: [sqlite] Most wanted features of SQLite ?

Jay A. Kreibich wrote: > On Sat, Sep 19, 2009 at 01:14:56PM -0700, Darren Duncan scratched on the wall: >> 3c. I would like to have the option for SQLite to never have duplicate >> unqualified column names; for example, if one said "foo NATURAL INNER >> JOIN bar" then only a single column with

Re: [sqlite] Most wanted features of SQLite ?

On Sat, Sep 19, 2009 at 01:14:56PM -0700, Darren Duncan scratched on the wall: > 3c. I would like to have the option for SQLite to never have duplicate > unqualified column names; for example, if one said "foo NATURAL INNER > JOIN bar" then only a single column with the common data would be in

Re: [sqlite] Most wanted features of SQLite ?

The word 'Stored Procedures ' when used in the context of DBMS is used to refer to several meanings: 1. Efficiency - compile once when 'stored' and run multiple-times. 2. Data Encapsulation & Access control for DB - DB owns and controls access to its API 'stored' in it. 3.

Re: [sqlite] Most wanted features of SQLite ?

Alexey Pechnikov wrote: > Hello! > > On Sunday 20 September 2009 00:14:56 Darren Duncan wrote: >> 3b. I would like to have the option for SQLite to always operate using >> 2-valued-logic rather than 3-valued-logic, meaning that NULL is simply >> treated >> as another value of its own

Re: [sqlite] Most wanted features of SQLite ?

Hello! On Sunday 20 September 2009 00:14:56 Darren Duncan wrote: > 3b. I would like to have the option for SQLite to always operate using > 2-valued-logic rather than 3-valued-logic, meaning that NULL is simply > treated > as another value of its own singleton type that is disjoint from all

Re: [sqlite] Most wanted features of SQLite ?

On Sat, 19 Sep 2009 21:57:13 +0100, Simon Slavin wrote: > >On 19 Sep 2009, at 9:14pm, Darren Duncan wrote: > >> Simon Slavin wrote: >>> On 18 Sep 2009, at 9:43pm, Noah Hart wrote: Stored Procedures >>> >>> How do those differ from what can be done with triggers

Re: [sqlite] Most wanted features of SQLite ?

On 19 Sep 2009, at 9:14pm, Darren Duncan wrote: > Simon Slavin wrote: >> On 18 Sep 2009, at 9:43pm, Noah Hart wrote: >>> Stored Procedures >> >> How do those differ from what can be done with triggers ? > > A stored procedure is an arbitrary-sized named sequence of > statements to > execute,

Re: [sqlite] Most wanted features of SQLite ?

Simon Slavin wrote: > On 18 Sep 2009, at 9:43pm, Noah Hart wrote: >> Stored Procedures > > How do those differ from what can be done with triggers ? A stored procedure is an arbitrary-sized named sequence of statements to execute, which is stored in the database as data (same as table or view

Re: [sqlite] Most wanted features of SQLite ?

On 18.09.2009 21:56 CE(S)T, Simon Slavin wrote: > * Support for multiple concurrent clients/processes Doesn't that already work? You need common file system access, right, but then it should work afaik. What I'd like to see is foreign key integrity enforcement. You can already do it with

Re: [sqlite] Most wanted features of SQLite ?

Hello! On Saturday 19 September 2009 02:32:03 Roger Binns wrote: > If you are using the C api then use > sqlite3_auto_extension - http://www.sqlite.org/c3ref/auto_extension.html - > to register a callback that is called whenever a new db is opened. For "autoload" extension we must call this

Re: [sqlite] Most wanted features of SQLite ?

On Sat, Sep 19, 2009 at 9:21 AM, John Stanton wrote: > Alexey Pechnikov wrote: >> Hello! >> >> On Saturday 19 September 2009 00:43:18 Noah Hart wrote: >> >>> Stored Procedures >>> >> >> There are Tiny C compiler extension and realization of >> stored procedures for SQLite 2

Re: [sqlite] Most wanted features of SQLite ?

Hello! On Saturday 19 September 2009 02:17:39 Subsk79 wrote: > StepSqlite brings powerful Stored Procedure support with full power of > PL/SQL syntax to SQLite. It is a 'compiler' as opposed to a mere > 'wrapper' so it generates much more efficient code than any wrapper > could ever achieve

Re: [sqlite] Most wanted features of SQLite ?

Hello! On Saturday 19 September 2009 18:21:22 John Stanton wrote: > There is a PL/SQL implementation available and we use Javascript as a > stored procedure capability in Sqlite. It integrates nicely with WWW > applications. I don't know this. Can you show link to docs and examples? Thx.

Re: [sqlite] Most wanted features of SQLite ?

Alexey Pechnikov wrote: > Hello! > > On Saturday 19 September 2009 00:43:18 Noah Hart wrote: > >> Stored Procedures >> > > There are Tiny C compiler extension and realization of > stored procedures for SQLite 2 and Lua extension and other. > So you can use one or all of these. > > Best

Re: [sqlite] Most wanted features of SQLite ?

On 19 Sep 2009, at 3:07am, Igor Tandetnik wrote: > Simon Slavin wrote: >> Thanks to you and Jay for explanations. I hadn't encountered ICU at >> all before. Your descriptions make perfect sense and are very >> interesting since ICU is a good attempt to get around one of the >> fundamental

Re: [sqlite] Most wanted features of SQLite ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hamish Allan wrote: > Not sure whether this would need a rewrite, but for debug purposes I'd > love to be able to view the SQL for a prepared statement with its > values bound. I am always confused by requests like this. Your code called prepare and

Re: [sqlite] Most wanted features of SQLite ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Slavin wrote: > Your descriptions make perfect sense and are very > interesting since ICU is a good attempt to get around one of the > fundamental problems of Unicode. Errr, this is not the fault of Unicode. It is the fault of people!

Re: [sqlite] Most wanted features of SQLite ?

Simon Slavin wrote: > Thanks to you and Jay for explanations. I hadn't encountered ICU at > all before. Your descriptions make perfect sense and are very > interesting since ICU is a good attempt to get around one of the > fundamental problems of Unicode. Out of curiosity - what do you consider

Re: [sqlite] Most wanted features of SQLite ?

On 19 Sep 2009, at 12:55am, Igor Tandetnik wrote: > Using ICU extension does require certain discipline. You must run > icu_load_collation soon after opening the database, and all users of > the > database must agree to map the same identifiers to the same locales > (the > best way to

Re: [sqlite] Most wanted features of SQLite ?

On Sat, Sep 19, 2009 at 12:14:37AM +0100, Simon Slavin scratched on the wall: > > On 18 Sep 2009, at 9:57pm, Igor Tandetnik wrote: > > > Simon Slavin > > wrote: > >> On 18 Sep 2009, at 9:07pm, Roger Binns wrote: > >> > >>> Simon Slavin wrote: > * Unicode

Re: [sqlite] Most wanted features of SQLite ?

Simon Slavin wrote: > On 18 Sep 2009, at 9:57pm, Igor Tandetnik wrote: > >> Simon Slavin >> wrote: >>> On 18 Sep 2009, at 9:07pm, Roger Binns wrote: >>> Simon Slavin wrote: > * Unicode support from the ground up SQLite

Re: [sqlite] Most wanted features of SQLite ?

On 18 Sep 2009, at 9:57pm, Igor Tandetnik wrote: > Simon Slavin > wrote: >> On 18 Sep 2009, at 9:07pm, Roger Binns wrote: >> >>> Simon Slavin wrote: * Unicode support from the ground up >>> >>> SQLite already has "unicode support from the ground up". Try using

Re: [sqlite] Most wanted features of SQLite ?

On 18 Sep 2009, at 9:43pm, Noah Hart wrote: > Stored Procedures How do those differ from what can be done with triggers ? Simon. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Most wanted features of SQLite ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Noah Hart wrote: > Stored Procedures Stored procedures don't make sense as a core part of SQLite because there is no one solution that fits all. For example what language would you write them in, and how would you deal with security (blindly loading

Re: [sqlite] Most wanted features of SQLite ?

StepSqlite brings powerful Stored Procedure support with full power of PL/SQL syntax to SQLite. It is a 'compiler' as opposed to a mere 'wrapper' so it generates much more efficient code than any wrapper could ever achieve - for instance, it pre-compiles all SQL in your code right when the

Re: [sqlite] Most wanted features of SQLite ?

t: [sqlite] Most wanted features of SQLite ? So if you had a team of programmers to write something like SQLite which didn't have the drawbacks SQLite has, which drawbacks would you identify ? I'm asking not about minor faults with specific SQLite library calls, but about the sort of things whi

Re: [sqlite] Most wanted features of SQLite ?

> On 18 Sep 2009, at 9:07pm, Roger Binns wrote: > > > Simon Slavin wrote: > >> * Unicode support from the ground up > > > > SQLite already has "unicode support from the ground up". Try using > > non-Unicode strings and you'll see! > > SQLite's indexing correctly understands how to order Unicode

Re: [sqlite] Most wanted features of SQLite ?

Simon Slavin wrote: > On 18 Sep 2009, at 9:07pm, Roger Binns wrote: > >> Simon Slavin wrote: >>> * Unicode support from the ground up >> >> SQLite already has "unicode support from the ground up". Try using >> non-Unicode strings and you'll see! > > SQLite's indexing

Re: [sqlite] Most wanted features of SQLite ?

Hello! On Saturday 19 September 2009 00:43:18 Noah Hart wrote: > Stored Procedures There are Tiny C compiler extension and realization of stored procedures for SQLite 2 and Lua extension and other. So you can use one or all of these. Best regards, Alexey Pechnikov. http://pechnikov.tel/

Re: [sqlite] Most wanted features of SQLite ?

080/cgi-bin/mailman/listinfo/sqlite-users > > -- View this message in context: http://www.nabble.com/Most-wanted-features-of-SQLite---tp25514570p25515213.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list

Re: [sqlite] Most wanted features of SQLite ?

On 18 Sep 2009, at 9:07pm, Roger Binns wrote: > Simon Slavin wrote: >> * Unicode support from the ground up > > SQLite already has "unicode support from the ground up". Try using > non-Unicode strings and you'll see! SQLite's indexing correctly understands how to order Unicode strings ? It

Re: [sqlite] Most wanted features of SQLite ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Slavin wrote: > * Unicode support from the ground up SQLite already has "unicode support from the ground up". Try using non-Unicode strings and you'll see! The issue some developers have is that they also want collations, case comparisons etc

[sqlite] Most wanted features of SQLite ?

So if you had a team of programmers to write something like SQLite which didn't have the drawbacks SQLite has, which drawbacks would you identify ? I'm asking not about minor faults with specific SQLite library calls, but about the sort of things which require rewriting from the ground