[sqlite] trademark issue? - (was Re: Announcing the Madis project)

[Darren Duncan]

Elefterios Stamatogiannakis wrote:
> Madis is a extensible relational database system built upon the SQLite 
> database and with extensions written in Python (via APSW SQLite 
> wrapper). Its is developed at:
> 
> http://madis.googlecode.com
> 
> Due to Madis’ SQLite core, the database format of Madis is exactly the 
> same as SQLite’s one. This means that all SQLite databases are directly 
> usable with Madis.
> 
> Madis' enables to quickly develop (in Python) and test new relational 
> functions and virtual tables. SQL syntax extensions were also created to 
> simplify queries which use these functions.
> 
> Madis' main goal is to promote the handling of data related tasks within 
> an extended relational model. In doing so, it promotes the database, 
> from a support role (storing and retrieving data), to being a full data 
> processing system on its own. Madis already includes functions for file 
> import/export, keyword analysis, data mining tasks, fast indexing, 
> pivoting, statistics and workflow execution.


I am concerned with your choice of project name, "Madis", because there may be 
reasonable grounds for confusion between your project and my "Muldis" projects, 
which I have been releasing and promoting for about 3 years now (and for which 
I've had domain names for about 6 years).

See http://muldis.com/ for my projects' canonical url, which has links to said 
projects near the top.

Specifically, I have "Muldis D" and "Muldis Rosetta" projects released now, and 
I intend to use "Muldis" as the distinguishing family identifier for other 
projects in the near future and over the long term.

My projects are relational+extended DBMSs and query languages and provide 
integration with both all general programming languages (starting with Perl, 
but 
Python being among the next top 3 to explicitly support) and existing SQL 
DBMSs, 
where SQLite would be one of the first.

Your project description sounds sufficiently similar.

While I can recognize how you might have independently come up with your name 
after following the above url (it looks like a combination of author name 
letters or institution letters), I hope that you can quickly come up with an 
alternative that isn't so similar to my name (say, by using some alternate 
letters from those sources, or making your name longer), and then use that from 
then on, and make an announcement of said name change as soon as possible.

If renaming "Madis" to something less similar to "Muldis" seems onerous or 
unnecessary, I welcome a reasonable proposal to resolve this matter.

Since it appears you only started promoting your project now, your name 
shouldn't have any mind share so I see little reason for you to keep it and 
have 
us add the complexity of explicit disclaimers of not being related to the other.

I also welcome any third party comments in regards to whether I have reasonable 
grounds to think there may be confusion between the 2 projects that could 
affect 
trademark matters.

Thank you in advance.

-- Darren Duncan

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

Re: [sqlite] sqlite3_close ==> " library routine called out of sequence"

[Simon Slavin]

On 23 Feb 2010, at 10:06pm, Simon Slavin wrote:

> Change the two error messages so the first one has a '1' in it and the second 
> one has a '2' in it.  Then run it again and tell us which of the two error 
> messages is being shown.

Ignore that.  I got confused.  Heh heh.

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

Re: [sqlite] sqlite3_close ==> " library routine called out of sequence"

[Simon Slavin]

On 23 Feb 2010, at 5:44pm, newlog wrote:

> With the following code :
> 
> -
> 
> sqlite3*db = NULL;
> 
>  if( sqlite3_open( "D:\Test3.db", ) != SQLITE_OK )
>   {
>// Exit if error while opening.
>wxMessageBox( wxString( "Error while opening :\n") <<
> sqlite3_errmsg(db)  );
>sqlite3_close(db);
>return;
>  }
> 
> 
>  if( sqlite3_close( db ) != SQLITE_OK );
>{
>  // Exit if error on closing.
>  wxMessageBox( wxString("Error while closing : \n")   <<
> sqlite3_errmsg( db ));
>  return;
>}
> 
> 
> __
> 
> 
> A Message windo prompts : " Error while closing : library routine
> called out of sequence "

Change the two error messages so the first one has a '1' in it and the second 
one has a '2' in it.  Then run it again and tell us which of the two error 
messages is being shown.

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

[sqlite] LibraryRoutineCalledOutOfSequence -- wiki suggestion

[Jonathan Landis]

It doesn't look like the wiki is editable.  I suppose you have your
reasons for that.  On the page below, I have a suggestion.

http://www.sqlite.org/cvstrac/wiki?p=LibraryRoutineCalledOutOfSequence

It is my experience that you can get "library routine called out of
sequence" if you call sqlite3_step on statement that writes to the
database and the process doesn't have write permission to the directory
in which the database is located (or maybe the current directory, I'm
not sure which).

In an ideal world, the error message would tell you exactly what is
wrong, but I don't want to argue about that.  I'm hoping someone can
confirm that I am right about the behavior and add a note about it to
the wiki page, which I found when searching for help on this problem.
Perhaps it will save someone some frustration.

JKL

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

Re: [sqlite] sqlite3_close ==> " library routine called out of sequence"

[newlog]

OK,

With the following code :

-

sqlite3*db = NULL;

  if( sqlite3_open( "D:\Test3.db", ) != SQLITE_OK )
   {
// Exit if error while opening.
wxMessageBox( wxString( "Error while opening :\n") <<
sqlite3_errmsg(db)  );
sqlite3_close(db);
return;
  }


  if( sqlite3_close( db ) != SQLITE_OK );
{
  // Exit if error on closing.
  wxMessageBox( wxString("Error while closing : \n")   <<
sqlite3_errmsg( db ));
  return;
}


__


A Message windo prompts : " Error while closing : library routine
called out of sequence "


I have to say that the statement sqlite3_open works fine because I
have no error on opening and I can successfully write/retrieve data in
the Test3.db database file.


I really don't understand



On Feb 23, 6:02 pm, Simon Davies 
wrote:
> On 23 February 2010 16:46, newlog  wrote:
>
> > Hi Simon,
>
> > Thanx for your answer,
>
> > IN case of error when trying to open the file, we close db pointer and
> > exit the sub-routine ( return keyword follows closing ).
>
> > So 'sqlite3_close' can't be called twice.
>
> My point was that if the database open has failed, then close will
> provoke MISUSE
>
>
>
> > Sincerely,
>
> > John
>
> Regards,
> Simon
> ___
> sqlite-users mailing list
> sqlite-us...@sqlite.orghttp://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] SQLite BUSY error - single-threaded app

[Alan Thomas]

The application runs as a singleton; there are no other applications
accessing the data base.

I do not run the command-line tool while testing.

I've cut down the example code:

  SqlStatus = sqlite3_open16 ( db_loc_string
 , 
 ) ;
  if ( SQLITE_OK != SqlStatus )
  {
. . .
return DATASTORE_UNAVAILABLE ;
  }

  SqlStatus = sqlite3_prepare16_v2 ( SqlDB
   , L"BEGIN TRANSACTION"
   , 36
   , 
   , NULL
   ) ;
  if ( SQLITE_OK != SqlStatus )
  {
. . .
return SQL_PREP_ERROR ;
  }

  SqlStatus = sqlite3_step ( SqlStmt ) ;
  if ( SQLITE_DONE != SqlStatus )
  {
. . .
return TXN_BEGIN_FAILED ;
  }

  SqlStatus = sqlite3_finalize ( SqlStmt ) ; SqlStmt = NULL ;
  if ( SQLITE_OK != SqlStatus )
  {
. . .
return SQL_FNLZ_ERROR ;
  }

  swprintf_s ( (PXID_CHAR)sql_statement
 , sizeof ( sql_statement ) / sizeof ( XID_CHAR )
 ,   L"DELETE"
  L" FROM RSPNS"
 L" WHERE . . .
 ) ;
  SqlStatus = sqlite3_prepare16_v2 ( SqlDB
   , sql_statement
   , ( lstrlen ( sql_statement ) + 1 ) *
sizeof ( XID_CHAR )
   , 
   , NULL
   ) ;
  if ( SQLITE_OK != SqlStatus )
  {
. . .
return SQL_PREP_ERROR ;
  }

  SqlStatus = sqlite3_step ( SqlStmt ) ;
  if ( SQLITE_DONE != SqlStatus )
  {
. . .
return SQL_DLET_ERROR ;
  }

  SqlStatus = sqlite3_finalize ( SqlStmt ) ; SqlStmt = NULL ;
  if ( SQLITE_OK != SqlStatus )
  {
. . .
return SQL_FNLZ_ERROR ;
  }

  SqlStatus = sqlite3_prepare16_v2 ( SqlDB
   , L"COMMIT TRANSACTION"
   , 38
   , 
   , NULL
   ) ;
  if ( SQLITE_OK != SqlStatus )
  {
. . .
return SQL_PREP_ERROR ;
  }

  SqlStatus = sqlite3_step ( SqlStmt ) ;
  if ( SQLITE_DONE != SqlStatus )
  {
. . .
return TXN_COMMIT_FAILED ;
  }

  SqlStatus = sqlite3_finalize ( SqlStmt ) ; SqlStmt = NULL ;
  if ( SQLITE_OK != SqlStatus )
  {
. . .
return SQL_FNLZ_ERROR ;
  }

  SqlStatus = sqlite3_prepare16_v2 ( SqlDB
   , L"BEGIN TRANSACTION"
   , 36
   , 
   , NULL
   ) ;
  if ( SQLITE_OK != SqlStatus )
  {
. . .
return SQL_PREP_ERROR ;
  }

  /*-*/

  SqlStatus = sqlite3_step ( SqlStmt ) ;
  if ( SQLITE_DONE != SqlStatus )
  {
. . .
return TXN_BEGIN_FAILED ;
  }

  SqlStatus = sqlite3_finalize ( SqlStmt ) ; SqlStmt = NULL ;
  if ( SQLITE_OK != SqlStatus )
  {
. . .
return SQL_FNLZ_ERROR ;
  }

  . . .

  swprintf_s ( (PXID_CHAR)sql_statement
 , sizeof ( sql_statement ) / sizeof ( XID_CHAR )
 ,   L"INSERT"
  L" INTO RSPNS"
 L" ( SERVER_NAME"
 . . .
 L" , RESPONSE_TEXT"
  L" )"
   L" VALUES ( '%s'"
 . , ,
  L" , '%s'"
  L" )"
 , ServerName
 . . .
 , [m]
 ) ;

 SqlStatus = sqlite3_prepare16_v2 ( SqlDB
  , (const char *)sql_statement
  , ( lstrlen ( sql_statement ) + 1 ) *
sizeof ( XID_CHAR )
  , 
  , NULL
  ) ;
 if ( SQLITE_OK != SqlStatus )
 {
   SQLiteError ( sql_statement
   , L"sqlite3_prepare16_v2 ( )"
   ) ;
   sqlite3_close ( SqlDB ) ; SqlDB = NULL ;
   return SQL_PREP_ERROR ;
 }

 SqlStatus = sqlite3_step ( SqlStmt ) ;
 if ( SQLITE_DONE != SqlStatus )
 {
   . . . 
   return SQL_ISRT_ERROR ;
 }

 SqlStatus = sqlite3_finalize ( SqlStmt ) ;
 if ( SQLITE_OK != SqlStatus )
 {
   . . . 
   return XID_DBPA_SQL_FNLZ_ERROR ;
 }

  . . .

 SqlStatus = sqlite3_prepare16_v2 ( SqlDB
  , L"COMMIT TRANSACTION"
  , 38
  , 
  , NULL
  ) ;
 if ( SQLITE_OK != SqlStatus )
 {
   . . . 
   return XID_DBPA_SQL_PREP_ERROR ;
 }

 SqlStatus = sqlite3_step ( SqlStmt ) ;
 if ( SQLITE_DONE != SqlStatus )
 {
   . . . 
   return XID_DBPA_TXN_COMMIT_FAILED ;
 }

 SqlStatus = sqlite3_finalize ( SqlStmt 

[sqlite] Announcing the Madis project

[Elefterios Stamatogiannakis]

Madis is a extensible relational database system built upon the SQLite 
database and with extensions written in Python (via APSW SQLite 
wrapper). Its is developed at:

http://madis.googlecode.com

Due to Madis’ SQLite core, the database format of Madis is exactly the 
same as SQLite’s one. This means that all SQLite databases are directly 
usable with Madis.

Madis' enables to quickly develop (in Python) and test new relational 
functions and virtual tables. SQL syntax extensions were also created to 
simplify queries which use these functions.

Madis' main goal is to promote the handling of data related tasks within 
an extended relational model. In doing so, it promotes the database, 
from a support role (storing and retrieving data), to being a full data 
processing system on its own. Madis already includes functions for file 
import/export, keyword analysis, data mining tasks, fast indexing, 
pivoting, statistics and workflow execution.

Some of the functionality of Madis is:

- Programmable (in Python) row functions (via APSW):

mterm> select detectlang('Il en est des livres comme du feu de nos foyers');
french

- Programmable (in Python) aggregate functions (via APSW):

mterm> select concatterms(a)
from (select "term1+term2" as a UNION select "term2 term3" as a);
term1+term2 term2 term3

- Programmable (in Python) virtual tables (via APSW):

mterm> select * from file('./demo/continents.tsv') limit 2;
Asia|AF
Europe|AL

- Multisets (functions that return multiple rows/columns):

mterm> select * from table1;
a |b
---
'car wood bike'| 'first group'
'car car wood'  |'first group'
'car wood'|'first group'
'car wood ice'  |'first group'
'ice'  |'second group'
'car ice'|'second group'
'car cream'  |'second group'
'icecream ice car'  |'second group'

mterm> select b, freqitemsets(a, 'threshold:2', 'noautothres:1', 
'maxlen:2') from table1 group by b
b| itemset_id | itemset_length | itemset_frequency | item
-
first group  | 1  | 1  | 4 | wood
first group  | 2  | 1  | 4 | car
first group  | 3  | 2  | 4 | car
first group  | 3  | 2  | 4 | wood
second group | 1  | 1  | 3 | ice
second group | 2  | 1  | 3 | car
second group | 3  | 2  | 2 | car
second group | 3  | 2  | 2 | ice

- On the fly multidimensional indexing (the cache virtual table):

The index is based on kdtrees and is extremely fast with queries 
involving multiple constraints.

mterm> select country.c2, continent.c1
   from file('countries.tsv') as country,
file('continents.tsv') as continent
   where country.c1=continent.c2;
Aruba|Americas
Antigua and Barbuda|Americas
United Arab Emirates|Asia
Afghanistan|Asia
. . . . . . . . .
Query executed in 0 min 2 sec 40 msec

mterm> select country.c2, continent.c1
   from file('countries.tsv') as country,
(CACHE file 'continents.tsv') as continent
   where country.c1=continent.c2;
Aruba|Americas
Antigua and Barbuda|Americas
United Arab Emirates|Asia
Afghanistan|Asia
. . . . . . . . .
Query executed in 0 min 0 sec 71 msec

- Workflows:

mterm> exec flow file 'workflow.sql';

Above query uses Madis' SQL inverted syntax.

- Pivoting:

http://madis.googlecode.com/svn/publish/row.html#pivoting

--

All above functionality has been created via row/aggregate/vtable Python 
extensions (APSW offers these in very nice API), and the aforementioned 
SQL syntax extensions.

In practise Madis has been proven to be very fast in data analysis tasks 
and in the development of data processing workflows.

A little note:

The high quality of APSW's and SQLite's code, has helped immensely in 
developing Madis. We have strained both of these projects as much as we 
could, and they coped beautifully. We literally had queries that spanned 
multiple pages, which executed in seconds.


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

Re: [sqlite] sqlite3_close ==> " library routine called out of sequence"

[Simon Davies]

On 23 February 2010 16:46, newlog  wrote:
> Hi Simon,
>
> Thanx for your answer,
>
>
> IN case of error when trying to open the file, we close db pointer and
> exit the sub-routine ( return keyword follows closing ).
>
> So 'sqlite3_close' can't be called twice.

My point was that if the database open has failed, then close will
provoke MISUSE

>
> Sincerely,
>
> John
>

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

Re: [sqlite] sqlite3_close ==> " library routine called out of sequence"

[newlog]

Hi Simon,

Thanx for your answer,


IN case of error when trying to open the file, we close db pointer and
exit the sub-routine ( return keyword follows closing ).

So 'sqlite3_close' can't be called twice.

Sincerely,

John



On Feb 23, 2:40 pm, Simon Davies 
wrote:
> On 23 February 2010 12:51, John  wrote:> Forgot to say 
> that the error occurs at the sqlite3_close   function.
>
> > John
>
> >> The very simple C-code below returns error message " library routine
> >> called out of sequence" .
> >> I really don't understand why  ?
>
> >> I'm using SQLite 3.6.22 under Windows XP
>
> >> Any idea/suggestion would be really appreciated !
>
> .
> .
> .
>
> >> Thanx for your help,
>
> >> John
>
> There are 2 calls to sqlite3_close in your code snippet. If the error
> occurs on the first, then the open has failed, and the error on close
> is probably the expected result.
>
> Regards,
> Simon
> ___
> sqlite-users mailing list
> sqlite-us...@sqlite.orghttp://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] Bug Report: DateTime incorrect for Windows

[Shane Harrelson]

On Tue, Feb 23, 2010 at 1:56 AM, 4eanlss <4ean...@engineer.com> wrote:

> Shane Harrelson  writes:
>
> >
> > I was unable to duplicate your error with the CLI and 3.6.22 (compiled
> with
> > cygwin\gcc or msvc):
> Ok, so Borland not supported and windows API not followed.
> Just as I expected from open source software.
>
>

I never said Borland was not supported.  I said I wasn't able to reproduce
the problem with the two compilers currently available to me.   It would be
very difficult to maintain build environments for every compiler and
compiler version used by SQLite users.
If you check the full source, you'll see where we've made specific
modifications for many compilers not used by us, like the Borland compilers,
all done and tested with the help of users.

I'm not certain what you mean by "windows API not followed".  Could you
provide more information?  In non CE builds, the only Windows API called in
the winCurrentTime() function is GetSystemTimeAsFileTime(). This returns a
FILETIME structure containing two DWORDS (u32s) representing the the number
of 100-nanosecond intervals since January 1, 1601.

The MSDN docs on the Windows API that use and manipulate system time values
state that it will be zero or positive, and less than 0x8000
(except for functions such as SetFileTime() which use 0x to
indicate that the previous file time should be preserved.)   Regardless, an
int64 is large enough to represent all the 100-nanosecond intervals from
January 1, 1601 through sometime in the year 30,828.

We use casting and 64-bit math to convert and manipulate these two DWORDS as
64-bit *signed *integers.   We avoid using uint64s because it's difficult
enough working through all the various compiler quirks out there for
manipulating 64-bit types with just int64s without introducing another
type.   Case in point, the odd initialization of some of the "consts" we use
in the winCurrentTime() function and the use of "math" instead of shifting.

I suspect that one of these "quirks" in your build environment is being
exposed by the code in winCurrentTime().Perhaps you could debug through
the code and find where the calculations are going wrong?   In this way we
could provide more help.

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

[sqlite] Unable to recover the DB by vacuum

[ramesh.kotabagi]

Thanks lot Pavel,
 
 >I only had two problem tables and luckily these seldom change,  for
these I went back to the week old backup and cut them out of the dump
file and applied them to the newly created database. Now I
integrity_check more often
 
i will try out ".dump option", i done last time also, i didn't able to
recover the complete DB,
the removing the some corrupt rows might have helped me, i will try out
this, thanks JIM
 

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email. 

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

[sqlite] Usage of vacuum and auto vacuum

[ramesh.kotabagi]

In which version of SQLite does this happen?
 
I am using version-3.5.8

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email. 

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

Re: [sqlite] sqlite3_close ==> " library routine called out of sequence"

[Nick Shaw]

What's the actual code output from your program?  i.e. which
sqlite3_close() is it failing on?

Can you call sqlite3_errmsg() when sqlite3_open() failed to initialise
the db struct?  I would have thought "db" would be invalid at that
point.  Try setting db to NULL when declaring it, as otherwise you may
be calling sqlite3_errmsg() with a non-null invalid pointer (it'll be
some random memory address if it's not nullified by sqlite3_open() on
open failure), which sqlite3 attempts to use but fails, resulting in
your "library routine called out of sequence" error?

Nick.

-Original Message-
From: sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of John
Sent: 23 February 2010 10:17
To: sqlite-users@sqlite.org
Subject: [sqlite] sqlite3_close ==> " library routine called out of
sequence"



Hi All,

The very simple C-code below returns error message " library routine
called out of sequence" .
I really don't understand why  ?

I'm using SQLite 3.6.22 under Windows XP

Any idea/suggestion would be really appreciated !


-
 sqlite3*db;
 sqlite3_stmt   *statement;
 wxStringTMPstring;


  if( sqlite3_open( "Test3.db", ) )
  { TMPstring << "Failed opening databse file:\n" <<
sqlite3_errmsg(db);
wxMessageBox( TMPstring );
sqlite3_close(db);
return;
  }


if( sqlite3_close( db ) != SQLITE_OK );
{   wxMessageBox( wxString("Database can not be closed
properly !\n\n")   << sqlite3_errmsg( db ));
return( -1 );
}

-


Thanx for your help,


John



___
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] Unable to recover the DB by vacuum

[Jim "Jed" Dodgen]

I recently had a similar problem,  not wanting to fall back to a week
old dump of the database, what I did was to command line ".dump"ed the
defective database and attempt a reload.
I only had two problem tables and luckily these seldom change,  for
these I went back to the week old backup and cut them out of the dump
file and applied them to the newly created database. Now I
integrity_check more often.

On Tue, Feb 23, 2010 at 3:54 AM, Pavel Ivanov  wrote:
>> How can i recover this kind of DB, is it possible? and is there any way
>> to avoid these
>> unused pages, will enable auto_vacuum solve the problem ?
>
> 'VACUUM' is not designed to recover malformed database. Yes, there are
> some kinds of problems that can be eliminated during vacuuming, but
> not all of them. And automatic vacuuming will never guarantee you
> protection against database corruption. When properly used SQLite will
> protect from database corruption itself. If you've got corrupted
> database it means that you have either bad application or your
> database file resides on some bad file system.
>
>
> Pavel
>
> On Tue, Feb 23, 2010 at 5:33 AM,   wrote:
>> Hi All,
>>
>> I found the DB corruption (malformed database), reporting some unused
>> pages,
>> please find the below trace,
>>
>> *** in database main ***
>> Main freelist: 21 of 21 pages missing from overflow list starting at 0
>> Page 1604: sqlite3BtreeInitPage() returns error code 11
>> Page 1461 is never used
>> Page 1468 is never used
>> Page 1469 is never used
>> Page 1472 is never used
>> Page 1473 is never used
>> Page 1474 is never used
>> Page 1475 is never used
>> Page 1478 is never used
>> Page 1480 is never used
>> Page 1482 is never used
>> Page 1484 is never used
>> Page 1485 is never used
>> Page 1486 is never used
>> Page 1488 is never used
>> Page 1489 is never used
>> Page 1491 is never used
>> Page 1517 is never used
>> Page 1531 is never used
>> Page 1536 is never used
>> Page 1578 is never used
>> Page 1581 is never used
>>
>> I tried to recover the DB, by running "vacuum", its failed again saying
>> "SQL error: database disk image is malformed".
>>
>> How can i recover this kind of DB, is it possible? and is there any way
>> to avoid these
>> unused pages, will enable auto_vacuum solve the problem ?
>>
>> I am using 3.5.8 version. and DB size is 1.6M
>>
>> Thanks in advance.
>>
>> Regards,
>> Ramesh
>>
>>
>> Please do not print this email unless it is absolutely necessary.
>>
>> The information contained in this electronic message and any attachments to 
>> this message are intended for the exclusive use of the addressee(s) and may 
>> contain proprietary, confidential or privileged information. If you are not 
>> the intended recipient, you should not disseminate, distribute or copy this 
>> e-mail. Please notify the sender immediately and destroy all copies of this 
>> message and any attachments.
>>
>> WARNING: Computer viruses can be transmitted via email. The recipient should 
>> check this email and any attachments for the presence of viruses. The 
>> company accepts no liability for any damage caused by any virus transmitted 
>> by this email.
>>
>> www.wipro.com
>> ___
>> 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
>



-- 
Jim "Jed" Dodgen
j...@dodgen.us
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] sqlite3_close ==> " library routine called out of sequence"

[Simon Davies]

On 23 February 2010 12:51, John  wrote:
> Forgot to say that the error occurs at the sqlite3_close   function.
>
> John
>
>> The very simple C-code below returns error message " library routine
>> called out of sequence" .
>> I really don't understand why  ?
>>
>> I'm using SQLite 3.6.22 under Windows XP
>>
>> Any idea/suggestion would be really appreciated !
>>
.
.
.
>> Thanx for your help,
>>
>> John

There are 2 calls to sqlite3_close in your code snippet. If the error
occurs on the first, then the open has failed, and the error on close
is probably the expected result.

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

Re: [sqlite] sqlite3_close ==> " library routine called out of sequence"

[John]

Forgot to say that the error occurs at the sqlite3_close   function.

John

On Feb 23, 11:17 am, John  wrote:
> Hi All,
>
> The very simple C-code below returns error message " library routine
> called out of sequence" .
> I really don't understand why  ?
>
> I'm using SQLite 3.6.22 under Windows XP
>
> Any idea/suggestion would be really appreciated !
>
> -
>  sqlite3        *db;
>  sqlite3_stmt   *statement;
>  wxString        TMPstring;
>
>   if( sqlite3_open( "Test3.db", ) )
>   {     TMPstring << "Failed opening databse file:\n" <<
> sqlite3_errmsg(db);
>         wxMessageBox( TMPstring );
>         sqlite3_close(db);
>         return;
>   }
>
>     if( sqlite3_close( db ) != SQLITE_OK );
>         {   wxMessageBox( wxString("Database can not be closed
> properly !\n\n")   << sqlite3_errmsg( db )    );
>             return( -1 );
>         }
>
> -
>
> Thanx for your help,
>
> John
>
> ___
> sqlite-users mailing list
> sqlite-us...@sqlite.orghttp://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] sqlite3_close ==> " library routine called out of sequence"

[John]

Hi All,

The very simple C-code below returns error message " library routine
called out of sequence" .
I really don't understand why  ?

I'm using SQLite 3.6.22 under Windows XP

Any idea/suggestion would be really appreciated !

-
 sqlite3*db;
 sqlite3_stmt   *statement;
 wxStringTMPstring;


  if( sqlite3_open( "Test3.db", ) )
  { TMPstring << "Failed opening databse file:\n" <<
sqlite3_errmsg(db);
wxMessageBox( TMPstring );
sqlite3_close(db);
return;
  }


if( sqlite3_close( db ) != SQLITE_OK );
{   wxMessageBox( wxString("Database can not be closed
properly !\n\n")   << sqlite3_errmsg( db ));
return( -1 );
}

-


Thanx for your help,


John



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

Re: [sqlite] Bug Report: DateTime incorrect for Windows

[4eanlss]

Shane Harrelson  writes:

> 
> I was unable to duplicate your error with the CLI and 3.6.22 (compiled with
> cygwin\gcc or msvc):
Ok, so Borland not supported and windows API not followed.
Just as I expected from open source software.





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

Re: [sqlite] Unable to recover the DB by vacuum

[Pavel Ivanov]

> How can i recover this kind of DB, is it possible? and is there any way
> to avoid these
> unused pages, will enable auto_vacuum solve the problem ?

'VACUUM' is not designed to recover malformed database. Yes, there are
some kinds of problems that can be eliminated during vacuuming, but
not all of them. And automatic vacuuming will never guarantee you
protection against database corruption. When properly used SQLite will
protect from database corruption itself. If you've got corrupted
database it means that you have either bad application or your
database file resides on some bad file system.


Pavel

On Tue, Feb 23, 2010 at 5:33 AM,   wrote:
> Hi All,
>
> I found the DB corruption (malformed database), reporting some unused
> pages,
> please find the below trace,
>
> *** in database main ***
> Main freelist: 21 of 21 pages missing from overflow list starting at 0
> Page 1604: sqlite3BtreeInitPage() returns error code 11
> Page 1461 is never used
> Page 1468 is never used
> Page 1469 is never used
> Page 1472 is never used
> Page 1473 is never used
> Page 1474 is never used
> Page 1475 is never used
> Page 1478 is never used
> Page 1480 is never used
> Page 1482 is never used
> Page 1484 is never used
> Page 1485 is never used
> Page 1486 is never used
> Page 1488 is never used
> Page 1489 is never used
> Page 1491 is never used
> Page 1517 is never used
> Page 1531 is never used
> Page 1536 is never used
> Page 1578 is never used
> Page 1581 is never used
>
> I tried to recover the DB, by running "vacuum", its failed again saying
> "SQL error: database disk image is malformed".
>
> How can i recover this kind of DB, is it possible? and is there any way
> to avoid these
> unused pages, will enable auto_vacuum solve the problem ?
>
> I am using 3.5.8 version. and DB size is 1.6M
>
> Thanks in advance.
>
> Regards,
> Ramesh
>
>
> Please do not print this email unless it is absolutely necessary.
>
> The information contained in this electronic message and any attachments to 
> this message are intended for the exclusive use of the addressee(s) and may 
> contain proprietary, confidential or privileged information. If you are not 
> the intended recipient, you should not disseminate, distribute or copy this 
> e-mail. Please notify the sender immediately and destroy all copies of this 
> message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient should 
> check this email and any attachments for the presence of viruses. The company 
> accepts no liability for any damage caused by any virus transmitted by this 
> email.
>
> www.wipro.com
> ___
> 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] Tcl VFS integration for Sqlite3

[Matthew Smith]

Thanks Alexey and Anton!
You guys really know your stuff!

This is a great help!  

-Original Message-
From: Alexey Pechnikov [mailto:pechni...@mobigroup.ru] 
Sent: Tuesday, 23 February 2010 21:35
To: sqlite-users@sqlite.org
Cc: Matthew Smith
Subject: Tcl VFS integration for Sqlite3

Hello!

See the solution here:
http://www.siftsoft.com/tclsqlitevfs.html

Best regards, Alexey Pechnikov.
http://pechnikov.tel/

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

[sqlite] Unable to recover the DB by vacuum

[ramesh.kotabagi]

Hi All,
 
I found the DB corruption (malformed database), reporting some unused
pages,
please find the below trace,
 
*** in database main ***
Main freelist: 21 of 21 pages missing from overflow list starting at 0
Page 1604: sqlite3BtreeInitPage() returns error code 11
Page 1461 is never used
Page 1468 is never used
Page 1469 is never used
Page 1472 is never used
Page 1473 is never used
Page 1474 is never used
Page 1475 is never used
Page 1478 is never used
Page 1480 is never used
Page 1482 is never used
Page 1484 is never used
Page 1485 is never used
Page 1486 is never used
Page 1488 is never used
Page 1489 is never used
Page 1491 is never used
Page 1517 is never used
Page 1531 is never used
Page 1536 is never used
Page 1578 is never used
Page 1581 is never used

I tried to recover the DB, by running "vacuum", its failed again saying
"SQL error: database disk image is malformed".
 
How can i recover this kind of DB, is it possible? and is there any way
to avoid these
unused pages, will enable auto_vacuum solve the problem ?
 
I am using 3.5.8 version. and DB size is 1.6M
 
Thanks in advance.
 
Regards,
Ramesh


Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email. 

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

[sqlite] Tcl VFS integration for Sqlite3

[Alexey Pechnikov]

Hello!

See the solution here:
http://www.siftsoft.com/tclsqlitevfs.html

Best regards, Alexey Pechnikov.
http://pechnikov.tel/
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] how to get the sqlite test case?

[A.]

The official test-suite is proprietary. If you really wish to get your
hands on it, you may enter in a contract with Hwaci as seen described at
http://sqlite.org/consortium.html

On Tue, 2010-02-23 at 08:55 +0800, xuecaili wrote:
> Hello!
> I'm a sqlite user and I want to use sqlite to develop a 
> software.  But at first, I'd like to test sqlite. It is declared in the 
> official web site that how sqlite is tested. I want to get the test case 
> you test the sqlite, especially 7.2 million queries run with the SQL 
> TEST LOGIC which is a test harness described in the web site. Can you 
> provide these 7.2 million queries?  I'll appreciate it!  Thank you very 
 I. much!


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