RE: [sqlite] SQLite 3.0...when???

[David LeBlanc]

> I have been using SQLite for over a year now and it is an excellent SQL
> Library. Some more features from SQL92 would surely be welcome
> while keeping
> SQLite fast and small. Suggestions for ver 3.0 include:
>
>   - Full referential integrity by implement check and foreign key
> constraints
>   - multi-row value inserts just like MySQL (..copied the REPLACE from
> MySQL..so copy INSERT as well)
>   - control-of-flow language such as IF-THEN-ELSE, BEGIN..END, WHILE,
> PRINT, RAISERROR, etc
>   - use of local variables e.g. DECLARE @varName dataType
>   - system global variables e.g. @@error, @@identity
>   - stored procedures: if triggers can be implemented then so can
> stored procs
>   - add alter TABLE, VIEW and TRIGGER
>   - CREATE, ALTER and DROP DATABASE: if we can attach and detach, we
> should also be able to create
>   and delete them through DDL statements
>
> I will be lucky if any of these would/could or should be
> implemented but if
> most were then even for embedded applications,
> being able to do almost all data manipulation using SQL statements only,
> would be a great improvement...
>
> B.Thomas

The likelihood of any of this being implemented varies in direct proportion
to how much of it you're willing to work on. Start something and people will
likely turn up to help. Ask for something and you're at the mercy of other
people's whims.

Incidentally, all these are good suggestions. ;-)

I'd love to see something along these lines (not SQL standard though AFAIK):
'PROCEDURE' 'LANGUAGE' '='
 '('')''{' '}'

Dave LeBlanc
Seattle, WA USA


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[sqlite] SQLite 3.0...when???

[basil . thomas]

I have been using SQLite for over a year now and it is an excellent SQL
Library. Some more features from SQL92 would surely be welcome while keeping
SQLite fast and small. Suggestions for ver 3.0 include:

- Full referential integrity by implement check and foreign key
constraints
- multi-row value inserts just like MySQL (..copied the REPLACE from
MySQL..so copy INSERT as well)
- control-of-flow language such as IF-THEN-ELSE, BEGIN..END, WHILE,
PRINT, RAISERROR, etc
- use of local variables e.g. DECLARE @varName dataType
- system global variables e.g. @@error, @@identity
- stored procedures: if triggers can be implemented then so can
stored procs
- add alter TABLE, VIEW and TRIGGER
- CREATE, ALTER and DROP DATABASE: if we can attach and detach, we
should also be able to create
and delete them through DDL statements

I will be lucky if any of these would/could or should be implemented but if
most were then even for embedded applications,
being able to do almost all data manipulation using SQL statements only,
would be a great improvement...

B.Thomas



This e-mail may be privileged and/or confidential, and the sender does not
waive any related rights and obligations. Any distribution, use or copying of
this e-mail or the information it contains by other than an intended recipient
is unauthorized. If you received this e-mail in error, please advise me (by
return e-mail or otherwise) immediately. 

Ce courrier électronique est confidentiel et protégé. L'expéditeur ne renonce
pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation
ou copie de ce message ou des renseignements qu'il contient par une personne
autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez
ce courrier électronique par erreur, veuillez m'en aviser immédiatement, par
retour de courrier électronique ou par un autre moyen.