Re: [sqlite] SQLite manager for Windows

[brettg]

SqlitePlus - www.sqliteplus.com

Quoting Edovia Technologies <[EMAIL PROTECTED]>:

> Hi,
>
>
>
> Anyone knows about a SQLite 3 manager for Windows? The only ones I've found
> so far seems to only be compatible with SQLite 2.
>
>
>
> Thanks!
>
>
>
> Luc Vandal
> Edovia Technologies Inc.
> [EMAIL PROTECTED]
> www.edovia.com
>
>
>
>
>
>
>
>





This message was sent using IMP, the Internet Messaging Program.

Re: [sqlite] SQLite manager for Windows

[mike cariotoglou]

look into www.sqlite.org/contrib

- Original Message - 
From: "Edovia Technologies" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 04, 2004 3:45 AM
Subject: [sqlite] SQLite manager for Windows


> Hi,
> 
>  
> 
> Anyone knows about a SQLite 3 manager for Windows? The only ones I've
> found
> so far seems to only be compatible with SQLite 2.
> 
>  
> 
> Thanks!
> 
>  
> 
> Luc Vandal
> Edovia Technologies Inc.
> [EMAIL PROTECTED]
> www.edovia.com
> 
>  
> 
>  
> 
>  
> 
> 

Re: [sqlite] SQLite manager for Windows

[杨军]

take a look at  
http://www.sqlite.org/contrib

>Hi,
>
> 
>
>Anyone knows about a SQLite 3 manager for Windows? The only ones I've found
>so far seems to only be compatible with SQLite 2.
>
> 
>
>Thanks!
>
> 
>
>Luc Vandal
>Edovia Technologies Inc.
>[EMAIL PROTECTED]
>www.edovia.com
>
> 
>
> 
>
> 
>
>


[EMAIL PROTECTED]
　　2004-11-04

[sqlite] SQLite manager for Windows

[Edovia Technologies]

Hi,

 

Anyone knows about a SQLite 3 manager for Windows? The only ones I've found
so far seems to only be compatible with SQLite 2.

 

Thanks!

 

Luc Vandal
Edovia Technologies Inc.
[EMAIL PROTECTED]
www.edovia.com

 

 

 

[sqlite] sample vbscript or wsh code

[Hensley, Bruce A]

I'm just looking into sqlite as a possible alternative for creating
databases to be accessed from small wsh or vbscript tools.  I've been
searching for an example, but have not yet found one.  A pointer would be
greatly appreciated.

Thanks.

Re: [sqlite] Release / development timeline

[David Fletcher]

> On Mon, 1 Nov 2004 19:23:58 -0800, Jonathon Blake
> <[EMAIL PROTECTED]> wrote:
> 
> How about a simple page that gives projected release date for upgrades?

I don't care about the release schedule as much as I care about the
release order.  The schedule will happen as it happens, and if I
really need to know I'm guessing that I can ask.  But, what I don't
know is who is working on what, and what's the priority for the
improvements?

I realize that some of this might be "shrouded" because of commercial
interests, but it would be most helpful to know that auto-vacuum will
be coming out next, which is what I'm guessing based on the recent
cvstrac activity.

An exhaustive list isn't essential.  It's a pain to update, anyway.  A
simple "top five" portion on the web page would serve me very well.

Just an opinion, and maybe not a good one.  But, thanks for listening,
and thanks for the great system.

-- 
David Fletcher  Tuscany Design Automation, Inc.
[EMAIL PROTECTED] 5875 S. Danube Circle
Aurora, CO 80015-3169 USA

Re: [sqlite] Release / development timeline

[Konstantin Malakhanov]

On 11/03/2004 02:16 PM, Peter Bartholdsson wrote:
> On Mon, 1 Nov 2004 19:23:58 -0800, Jonathon Blake
> <[EMAIL PROTECTED]> wrote:
> 
>> How about a simple page that gives projected release date for upgrades?
>>
>> Something like
>>
>> Version 3.0.9 beta  10 November
>> Version 3.0.9 final   20 November
>> Version 3.0.10 beta 1 December
>> Version 3.0.10 final 15 December
> 
> 
> All this would do is create pressure and people asking why stuff ain't
> done yet like the projected release date states. Especially since coders
> are optimists by nature when it comes to time estimates. :P
> 

It's always two weeks to the next release ;-)


-- 
Konstantin Malakhanov <[EMAIL PROTECTED]>

Re: [sqlite] Flush to disc

[Konstantin Malakhanov]

On 11/03/2004 08:48 PM, Reid Thompson wrote:
> [EMAIL PROTECTED] wrote:
> 
>>In a message dated 11/3/2004 12:20:36 PM Eastern Standard Time,
>>[EMAIL PROTECTED] writes: 
>>
>>How can  I make sure after an insert that everything has been flushed
>>to disc? 
>>
>>I  mean, I want even my program to become slower as long as I know
>> everything have been written to disc.
>>
>>At the moment I am using:
>>PRAGMA  default_synchronous = FULL;
>>PRAGMA synchronous = FULL;
>>
>>
>>And the  queries are all INSERT's without a  transaction.
>>
>>
>>Thx,
>>
>>KaReL (aka  Steven)
>>
>>Main Webpage : _http://www.karels0ft.be/
>>_ (http://www.karels0ft.be/) ICQ  #:  35217584
>>
>>
>>
>>If synchronus=FULL is set. every insert without a transaction is
>>flushed to disk before sqlite3_finalized is returned.  You are safe.
>>
>>Wei
> 
> 
> Unless you are using IDE disks that respond that they've written to the
> disk when in fact they have not.

..or you have some transaction-based/journaling filesystem which delays
data writing to disk ;-)

> reid
> 
> 


-- 
Konstantin Malakhanov <[EMAIL PROTECTED]>

RE: [sqlite] Flush to disc

[Reid Thompson]

[EMAIL PROTECTED] wrote:
> In a message dated 11/3/2004 12:20:36 PM Eastern Standard Time,
> [EMAIL PROTECTED] writes: 
> 
> How can  I make sure after an insert that everything has been flushed
> to disc? 
> 
> I  mean, I want even my program to become slower as long as I know
>  everything have been written to disc.
> 
> At the moment I am using:
> PRAGMA  default_synchronous = FULL;
> PRAGMA synchronous = FULL;
> 
> 
> And the  queries are all INSERT's without a  transaction.
> 
> 
> Thx,
> 
> KaReL (aka  Steven)
> 
> Main Webpage : _http://www.karels0ft.be/
> _ (http://www.karels0ft.be/) ICQ  #:  35217584
> 
> 
> 
> If synchronus=FULL is set. every insert without a transaction is
> flushed to disk before sqlite3_finalized is returned.  You are safe.
> 
> Wei

Unless you are using IDE disks that respond that they've written to the
disk when in fact they have not.

reid

RE: [sqlite] column def vs. constraint at end of create table stmt

[itIsMe]

>>You can see that the only way to create a two-column constraint is to
use 
>>this syntax (unless you want to define an index, that is).

>>Guy


hi -

I can see where I was confused now.
I will make the required changes.

thanks for your help,
jim

[sqlite] Flush to disc

[Steven Van Ingelgem]

How can I make sure after an insert that everything has been flushed to
disc?
I mean, I want even my program to become slower as long as I know
everything have been written to disc.
At the moment I am using:
PRAGMA default_synchronous = FULL;
PRAGMA synchronous = FULL;

And the queries are all INSERT's without a transaction.

Thx,

KaReL (aka Steven)
Main Webpage :
http://www.karels0ft.be/
ICQ #    :
35217584





pgpO7DHjniwta.pgp
Description: PGP signature

Re: [sqlite] column def vs. constraint at end of create table stmt

[Guy Hachlili]

At 18:57 11/2/2004 -0500, you wrote:
if I have a column def statement for every field and specify unique and
primary constraints in each column def, what is the reason the
constraint that goes on the very end of the create table would be needed
[, constraint]*  
 column-def ::= name [type] [[CONSTRAINT name] column-constraint]*
 sql-command ::= CREATE [TEMP | TEMPORARY] TABLE table-name (
column-def [, column-def]*
[, constraint]*
)
Some database users like to have constraints for more then one column at a 
time; for example, creating a unique constraint for two columns together. 
As constraint is defined thus:

constraint ::=  PRIMARY KEY ( column-list ) [ conflict-clause ] |
  UNIQUE ( column-list ) [ conflict-clause ] |
  CHECK ( expr ) [ conflict-clause ]
You can see that the only way to create a two-column constraint is to use 
this syntax (unless you want to define an index, that is).

Guy

RE: [sqlite] Pocket PC - SQLite - eMbedded Visual C++

[Stober, Mel]

yes

http://sqlite-wince.sf.net

Mel Stober
Tri-Cor Industries Inc./GATES AIT
618-632-9252 Ext 253



-Original Message-
From: nfr [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 03, 2004 8:09 AM
To: [EMAIL PROTECTED]
Subject: Re: [sqlite] Pocket PC - SQLite - eMbedded Visual C++


Aaron Planell López wrote:

> Hi:
>
> I’m trying to create an eMbedded Visual C++ application for Pocket PC 
> using SQLite.
>
> Is it possible?
>
> Thanks!
>
> Atentamente,
>
> *Aaron Planell López***
>
> Principal: [EMAIL PROTECTED] *
>
> Trabajo: [EMAIL PROTECTED] 
> 
>
> Facultad: [EMAIL PROTECTED] 
> 
>
> Proyecto: [EMAIL PROTECTED] 
>
> Messenger: [EMAIL PROTECTED] 
>
> GMail: [EMAIL PROTECTED] 
>
Yes, I do it with eVC3, use the CE port (i use the 2.8 version)

Noël

Re: [sqlite] Pocket PC - SQLite - eMbedded Visual C++

[nfr]

Aaron Planell López wrote:
Hi:
I’m trying to create an eMbedded Visual C++ application for Pocket PC 
using SQLite.

Is it possible?
Thanks!
Atentamente,
*Aaron Planell López***
Principal: [EMAIL PROTECTED] *
Trabajo: [EMAIL PROTECTED] 


Facultad: [EMAIL PROTECTED] 


Proyecto: [EMAIL PROTECTED] 
Messenger: [EMAIL PROTECTED] 
GMail: [EMAIL PROTECTED] 
Yes, I do it with eVC3, use the CE port (i use the 2.8 version)
Noël

[sqlite] Pocket PC - SQLite - eMbedded Visual C++

[Aaron Planell López]

Hi:

 

I’m trying
to create an eMbedded Visual C++ application for Pocket PC using SQLite.

Is it possible?

 

Thanks!

 



Atentamente,

Aaron Planell López

 

Principal:    [EMAIL PROTECTED]

Trabajo:    [EMAIL PROTECTED]

Facultad:   [EMAIL PROTECTED]

Proyecto:  [EMAIL PROTECTED]

Messenger:    [EMAIL PROTECTED]

GMail:    [EMAIL PROTECTED]

 

  




 

Re: [sqlite] Release / development timeline

[Peter Bartholdsson]

On Mon, 1 Nov 2004 19:23:58 -0800, Jonathon Blake <[EMAIL PROTECTED]> wrote:
How about a simple page that gives projected release date for upgrades?
Something like
Version 3.0.9 beta  10 November
Version 3.0.9 final   20 November
Version 3.0.10 beta 1 December
Version 3.0.10 final 15 December
All this would do is create pressure and people asking why stuff ain't
done yet like the projected release date states. Especially since coders
are optimists by nature when it comes to time estimates. :P

Re: [sqlite] sqlite3 problems on both 32 and 64 architectures

[D. Richard Hipp]

Jaros?aw Staniek wrote:
Hallo,
assertions like this (btree.c, line 1043) are bad:
  assert( sizeof(ptr)==sizeof(char*) );
The problem better is described here:
http://bugs.kde.org/show_bug.cgi?id=92563
Reporters say that even for intel P4, sizeof pointers is 8, not 4 there. 
Any plans for fixing these bugs in official sqlite release?

On the contrary, the assert show above is a Very Good Thing.
The ptr type is supposed to be a signed integer which is
the same size as a pointer.  The configure script is suppose
to run some tests to pick the appropriate integer size and
set a #define so that ptr can be defined appropriately.
The assert() above verifies that all this happened correctly.
In your case, there is some kind of configuration problem
and ptr is not being sized correctly.  The assert above
discovered this problem quickly so that you know the library
is miscompiled, rather than letting the library run and
generate subtle and hard-to-track errors.
You should be thankful for this assert.  I has saved you
a lot of debugging.
The configure script is suppose to set a macro named
SQLITE_PTR_SZ to either 4 or 8.  Like this:
-DSQLITE_PTR_SZ=8
-DSQLITE_PTR_SZ=4
What do you see when you compile?  4 or 8?  Why is the
configure script setting it incorrectly?
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565

[sqlite] Kexi 0.1 beta 5 released

[Jarosław Staniek]

(This is forwarded here because Kexi user SQLite as it's default db backend. 
See http://www.kexi-project.org/announce-0.1-beta5.html for more links.)

Kexi 0.1 beta 5 Announcement
DATELINE NOVEMBER 1, 2004
FOR IMMEDIATE RELEASE
November 1, 2004 (The INTERNET). The Kexi Team today announced the
immediate availability of Kexi 0.1 beta 5, codenamed "Halloween", the
newest preview release of the integrated environment for managing data
aimed at developers and experienced users.
Changes since beta 4 version
* Tens of improvements in KexiDB, Database Support Library (readded
MySQL support, SQLite3 support and migration to/from SQLite2 with unicode
characters, renewed SQL Parsing module)
* Much improved Form Designer (more widgets and editing actions,
subforms, KDevelop plugin mode, KFormDesigner mode)
* Much improved Table Designer (autonumbers, both Visual and SQL mode,
parser)
* Fixes in Query Designer
* Many fixes in Data Table View (new actions, more convenient
navigation and data editing)
* Overall application improvements (more error/problem messages,
actions, new command line options, better startup handling)
See also Detailed information on changes, Screenshots.
Download
Kexi and its libraries are available under flexible Open Source license
(LGPL). It can be obtained as Linux/Unix source code download.kde.org.
Note: FTP servers' mirroring may take even one day.
Jobs
"Ask not what Kexi can do for you, ask what you can do for Kexi"
Kexi Team is looking for developers, and package maintainers (vide
supported Linux distributions). Translators, testers, end-user and
development documentation writers, and any other forms of support are also
welcome. Contact us immediately.
How to compile Kexi
To learn how to compile Kexi, see this document.
Support
Kexi users are invited to report bugs and wishes. This can be done
directly to the Kexi Bug Database (please login as user "guest", without a
password). Bugs and wishes can be also reported to the KDE Bug Tracking
System.
Updated list of unsupported features and known problems is also available.
Kexi Sponsorship
Kexi is developed by Kexi Team - an international group of independent
developers, with assistance and workforce coming from the OpenOffice
Polska company.
About Kexi
Kexi is an integrated environment for managing data. It helps in creating
database schema, editing, inserting, querying and processing data. As Kexi
is a real member of the KDE and KOffice projects, it integrates fluently
into both on Linux/Unix. It is designed to be fully usable also without
running KDE Desktop on Linux/Unix, MS Windows and Mac OS X platforms.
Kexi is considered as long awaited MS Access replacement.
--
regards,
Kexi Team