[sqlite] Fixes to the transliteration table in ext/misc/spellfix.c

[Marcin Ciura]

In http://www.sqlite.org/src/artifact/b3a644285cb008f3:

  { 0x0392,  0x42, 0x00, 0x00, 0x00 },  /* Β to B */
  { 0x03B2,  0x62, 0x00, 0x00, 0x00 },  /* β to b */

Although Ancient Greek beta is rendered as B, Modern Greek beta is
transliterated as V:
https://en.wikipedia.org/wiki/Romanization_of_Greek#Modern_Greek

  { 0x040B,  0x44, 0x00, 0x00, 0x00 },  /* Ћ to D */
  { 0x045B,  0x64, 0x00, 0x00, 0x00 },  /* ћ to d */

This Serbian letter corresponds to Croatian Ć, so it should be
transliterated as C: https://en.wikipedia.org/wiki/Tshe

  { 0x0409,  0x49, 0x00, 0x00, 0x00 },  /* Љ to I */
  { 0x0459,  0x69, 0x00, 0x00, 0x00 },  /* љ to i */

This Serbian letter corresponds to the Croatian digraph Lj, so it should be
transliterated as L (probably not Lj for consistency with Њ transliterated
as N): https://en.wikipedia.org/wiki/Lje

  { 0x0426,  0x54, 0x63, 0x00, 0x00 },  /* Ц to Tc */
  { 0x0446,  0x74, 0x63, 0x00, 0x00 },  /* ц to tc */

This Cyrillic letter is usually transliterated as Ts.  Unless "Tc" is a
hack meant to cover both "Ts" and the rarer transliteration "C", it looks
like a typo: https://en.wikipedia.org/wiki/Tse_(Cyrillic)

Best regards,
Marcin Ciura
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Infinite loop in sqlite3VdbeSorterWrite when sorting big data

[Marcin Sobieszczanski]

> Thanks for reporting this. I think it should be fixed here:
>
>   http://www.sqlite.org/src/info/623827192532f08b

Thanks for the fix! I confirm it fixes the issue I saw.

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

Re: [sqlite] Infinite loop in sqlite3VdbeSorterWrite when sorting big data

[Marcin Sobieszczanski]

> Do you have a large cache-size configured?

Yes:

PRAGMA cache_size = 10
PRAGMA page_size = 16384
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Problem with SQLiteCommand.Parameters and CurrentCulture

[Marcin Szotka]

Hi
 
Look at example from attachement, please. In test
InsertDoubleByCommandWithParam you could see problem with storing double
by command with parameter. We use Flags=BindAndGetAllAsText.
 
It works: 
 
command.CommandText = "INSERT INTO EntA (Id, EntityProperty1,
DoubleProperty) VALUES (1, 'NaN', 'NaN'), (2, 'RegularDouble', '1.2'),
(3, 'PositiveInfinity', 'Infinity'), (4, 'NegativeInfinity',
'-Infinity')"; 
 
It doesn't work: 
 
command.CommandText = "INSERT INTO EntA (Id, EntityProperty1,
DoubleProperty) VALUES (1, 'NaN', 'NaN'), (2, 'RegularDouble',
@doubleProp), (3, 'PositiveInfinity', 'Infinity'), (4,
'NegativeInfinity', '-Infinity')";

command.Parameters.AddWithValue("@doubleProp", 1.2);

I work on Win 8.1 EN with Polish local settings. If I change 

command.Parameters.AddWithValue("@doubleProp", 1.2);

into

command.Parameters.AddWithValue("@doubleProp",
1.2.ToString(CultureInfo.InvariantCulture))

all work fine.

In my opinion command parameters should use InvariantCulture when
converting types to string.

 

Best Regards

Marcin Szotka - InstalSoft

 

 

 

 

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

Re: [sqlite] Malformed database recovery

[Marcin]

Of course, I understand that I haven't recovered everything, but as I said 
before, I don't find any big ammount of data lost ;)


Sent: Tuesday, May 14, 2013 5:59 PM
Subject: Re: [sqlite] Malformed database recovery




On 14 May 2013, at 4:54pm, "Marcin" <ign...@op.pl> wrote:

Ok, I had a great idea, and propably somehow managed to repair it. I 
opened dump_all.sql in notepad, deleted two "/ ERROR: (11) database 
disk image is malformed */", changed ROLLBACK into COMMIT, and it is 
working so far.


The ROLLBACK indicates that the dump routine got to a certain point and 
reached corruption.  So what you have now is a database which probably 
contains just /some but not all/ of your original records.  If this is 
better than nothing for you, then that's fine, but don't use it for a year 
before realising that you have lost vital data.


Simon.
___
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] Malformed database recovery

[Marcin]

Ok, I had a great idea, and propably somehow managed to repair it. I opened 
dump_all.sql in notepad, deleted two "/ ERROR: (11) database disk image 
is malformed */", changed ROLLBACK into COMMIT, and it is working so 
far.


ignac8

Sent: Tuesday, May 14, 2013 5:48 PM
Subject: Re: [sqlite] Malformed database recovery



If you can get the errors, by say redirecting the output from the .read to
a file, the error message will likely be enlightening.  When I recover
corrupt db files, there are often some records with a conflicting primary
key.   In those cases I have to edit the input to fix the old one.
Naturally, you desire a commit rather than a rollback when your .read can
execute with no errors.

Others on the list are far better at explaining the output of the 
integrity

check than I am.

Adam


On Tue, May 14, 2013 at 11:40 AM, Marcin <ign...@op.pl> wrote:


No errors, but tshockfixed.sqlite is empty, and in the end of file
dump_all.sql there is "ROLLBACK; -- due to errors".

It's was check of tshock.sqlite, old one.

ignac8

Sent: Tuesday, May 14, 2013 4:43 PM
Subject: Re: [sqlite] Malformed database recovery


 Where there any errors on


.read dump_all.sql ?

was PRAGMA integrity_check;  on the new file or the old one?


On Tue, May 14, 2013 at 10:29 AM, Marcin <ign...@op.pl> wrote:

 Hi everybody.


Somehow my database got malformed, and journal file is unfortunately
nowhere to found.

Suprisingly, I'm able to open it in Sqlite Database Browser, and read
stored values. There is only minor data loss, as I can't really see 
what

got missing. I've also managed to figure which table is damaged.

I've tried doing this:

sqlite3.exe tshock.sqlite
sqlite> .mode insert
sqlite> .output dump_all.sql
sqlite> .dump
sqlite> .exit
sqlite3.exe tshockfixed.sqlite
sqlite> .read dump_all.sql
sqlite> .exit

But it still returns malformed one.

PRAGMA integrity_check; returns this:

*** in database main ***
On tree page 3 cell 17: invalid page number 9049
On tree page 3 cell 17: Child page depth differs
On tree page 3 cell 18: Child page depth differs
On tree page 8948 cell 86: invalid page number 9047
On tree page 8948 cell 86: Child page depth differs
On tree page 8948 cell 87: invalid page number 9051
On tree page 8948 cell 88: invalid page number 9055
On tree page 8948 cell 89: Child page depth differs
On tree page 8948 cell 90: invalid page number 9061
On tree page 8948 cell 90: Child page depth differs
On tree page 8948 cell 91: invalid page number 9066
On tree page 8948 cell 92: invalid page number 9069
On page 8948 at right child: invalid page number 9074
On tree page 9039 cell 69: invalid page number 9046
On tree page 9039 cell 69: Child page depth differs
On tree page 9039 cell 70: invalid page number 9048
On tree page 9039 cell 71: invalid page number 9050
On tree page 9039 cell 72: invalid page number 9052
On tree page 9039 cell 73: invalid page number 9053
On tree page 9039 cell 74: invalid page number 9054
On tree page 9039 cell 75: invalid page number 9056
On tree page 9039 cell 76: invalid page number 9057
On tree page 9039 cell 77: invalid page number 9058
On tree page 9039 cell 78: invalid page number 9059
On tree page 9039 cell 79: invalid page number 9060
On tree page 9039 cell 80: invalid page number 9062
On tree page 9039 cell 81: invalid page number 9063
On tree page 9039 cell 82: invalid page number 9064
On tree page 9039 cell 83: invalid page number 9065
On tree page 9039 cell 84: invalid page number 9067
On tree page 9039 cell 85: invalid page number 9068
On tree page 9039 cell 86: invalid page number 9070
On tree page 9039 cell 87: invalid page number 9071
On tree page 9039 cell 88: invalid page number 9072
On tree page 9039 cell 89: invalid page number 9073
On tree page 9039 cell 90: invalid page number 9075
On tree page 9039 cell 91: invalid page number 9077
On page 9039 at right child: invalid page number 9076
Error: database disk image is malformed

Does anybody got an idea, and can help me?

ignac8

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





--
VerifEye Technologies Inc.
905-948-0015x245
151 Whitehall Dr, Unit 2
Markham ON, L3R 9T1
Canada
__**_
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-**bin/mailman/listinfo/sqlite-**users<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<http://sqlite.org:8080/cgi-bin/mailman/listinfo/sq

Re: [sqlite] Malformed database recovery

[Marcin]

No errors, but tshockfixed.sqlite is empty, and in the end of file 
dump_all.sql there is "ROLLBACK; -- due to errors".


It's was check of tshock.sqlite, old one.

ignac8

Sent: Tuesday, May 14, 2013 4:43 PM
Subject: Re: [sqlite] Malformed database recovery



Where there any errors on

.read dump_all.sql ?

was PRAGMA integrity_check;  on the new file or the old one?


On Tue, May 14, 2013 at 10:29 AM, Marcin <ign...@op.pl> wrote:


Hi everybody.

Somehow my database got malformed, and journal file is unfortunately
nowhere to found.

Suprisingly, I'm able to open it in Sqlite Database Browser, and read
stored values. There is only minor data loss, as I can't really see what
got missing. I've also managed to figure which table is damaged.

I've tried doing this:

sqlite3.exe tshock.sqlite
sqlite> .mode insert
sqlite> .output dump_all.sql
sqlite> .dump
sqlite> .exit
sqlite3.exe tshockfixed.sqlite
sqlite> .read dump_all.sql
sqlite> .exit

But it still returns malformed one.

PRAGMA integrity_check; returns this:

*** in database main ***
On tree page 3 cell 17: invalid page number 9049
On tree page 3 cell 17: Child page depth differs
On tree page 3 cell 18: Child page depth differs
On tree page 8948 cell 86: invalid page number 9047
On tree page 8948 cell 86: Child page depth differs
On tree page 8948 cell 87: invalid page number 9051
On tree page 8948 cell 88: invalid page number 9055
On tree page 8948 cell 89: Child page depth differs
On tree page 8948 cell 90: invalid page number 9061
On tree page 8948 cell 90: Child page depth differs
On tree page 8948 cell 91: invalid page number 9066
On tree page 8948 cell 92: invalid page number 9069
On page 8948 at right child: invalid page number 9074
On tree page 9039 cell 69: invalid page number 9046
On tree page 9039 cell 69: Child page depth differs
On tree page 9039 cell 70: invalid page number 9048
On tree page 9039 cell 71: invalid page number 9050
On tree page 9039 cell 72: invalid page number 9052
On tree page 9039 cell 73: invalid page number 9053
On tree page 9039 cell 74: invalid page number 9054
On tree page 9039 cell 75: invalid page number 9056
On tree page 9039 cell 76: invalid page number 9057
On tree page 9039 cell 77: invalid page number 9058
On tree page 9039 cell 78: invalid page number 9059
On tree page 9039 cell 79: invalid page number 9060
On tree page 9039 cell 80: invalid page number 9062
On tree page 9039 cell 81: invalid page number 9063
On tree page 9039 cell 82: invalid page number 9064
On tree page 9039 cell 83: invalid page number 9065
On tree page 9039 cell 84: invalid page number 9067
On tree page 9039 cell 85: invalid page number 9068
On tree page 9039 cell 86: invalid page number 9070
On tree page 9039 cell 87: invalid page number 9071
On tree page 9039 cell 88: invalid page number 9072
On tree page 9039 cell 89: invalid page number 9073
On tree page 9039 cell 90: invalid page number 9075
On tree page 9039 cell 91: invalid page number 9077
On page 9039 at right child: invalid page number 9076
Error: database disk image is malformed

Does anybody got an idea, and can help me?

ignac8

__**_
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-**bin/mailman/listinfo/sqlite-**users<http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users>





--
VerifEye Technologies Inc.
905-948-0015x245
151 Whitehall Dr, Unit 2
Markham ON, L3R 9T1
Canada
___
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

[sqlite] Malformed database recovery

[Marcin]

Hi everybody.

Somehow my database got malformed, and journal file is unfortunately nowhere 
to found.


Suprisingly, I'm able to open it in Sqlite Database Browser, and read stored 
values. There is only minor data loss, as I can't really see what got 
missing. I've also managed to figure which table is damaged.


I've tried doing this:

sqlite3.exe tshock.sqlite
sqlite> .mode insert
sqlite> .output dump_all.sql
sqlite> .dump
sqlite> .exit
sqlite3.exe tshockfixed.sqlite
sqlite> .read dump_all.sql
sqlite> .exit

But it still returns malformed one.

PRAGMA integrity_check; returns this:

*** in database main ***
On tree page 3 cell 17: invalid page number 9049
On tree page 3 cell 17: Child page depth differs
On tree page 3 cell 18: Child page depth differs
On tree page 8948 cell 86: invalid page number 9047
On tree page 8948 cell 86: Child page depth differs
On tree page 8948 cell 87: invalid page number 9051
On tree page 8948 cell 88: invalid page number 9055
On tree page 8948 cell 89: Child page depth differs
On tree page 8948 cell 90: invalid page number 9061
On tree page 8948 cell 90: Child page depth differs
On tree page 8948 cell 91: invalid page number 9066
On tree page 8948 cell 92: invalid page number 9069
On page 8948 at right child: invalid page number 9074
On tree page 9039 cell 69: invalid page number 9046
On tree page 9039 cell 69: Child page depth differs
On tree page 9039 cell 70: invalid page number 9048
On tree page 9039 cell 71: invalid page number 9050
On tree page 9039 cell 72: invalid page number 9052
On tree page 9039 cell 73: invalid page number 9053
On tree page 9039 cell 74: invalid page number 9054
On tree page 9039 cell 75: invalid page number 9056
On tree page 9039 cell 76: invalid page number 9057
On tree page 9039 cell 77: invalid page number 9058
On tree page 9039 cell 78: invalid page number 9059
On tree page 9039 cell 79: invalid page number 9060
On tree page 9039 cell 80: invalid page number 9062
On tree page 9039 cell 81: invalid page number 9063
On tree page 9039 cell 82: invalid page number 9064
On tree page 9039 cell 83: invalid page number 9065
On tree page 9039 cell 84: invalid page number 9067
On tree page 9039 cell 85: invalid page number 9068
On tree page 9039 cell 86: invalid page number 9070
On tree page 9039 cell 87: invalid page number 9071
On tree page 9039 cell 88: invalid page number 9072
On tree page 9039 cell 89: invalid page number 9073
On tree page 9039 cell 90: invalid page number 9075
On tree page 9039 cell 91: invalid page number 9077
On page 9039 at right child: invalid page number 9076
Error: database disk image is malformed

Does anybody got an idea, and can help me?

ignac8

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

[sqlite] BUG? sqlite not reporting error like "more than one row returned by a subquery used as an expression"

[Marcin Kałuża]

We've encountered strange sqlite behavior:

SQLite version 3.7.15.2 2013-01-09 11:53:05
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> create table t(v int4);
sqlite> insert into t values (1),(2),(3);
sqlite> select * from t where v = (select v from t);
1
sqlite> select * from t where v in (select v from t);
v
--
1
2
3

While on postgres it works like this (as far as I remember oracle does 
this as well, and that's the way it should work imho):

mail=> create table t (v int4);
CREATE TABLE
mail=> insert into t values (1),(2),(3);
INSERT 0 3
mail=> select * from t where v = (select v from t);
ERROR:  more than one row returned by a subquery used as an expression
mail=> select * from t where v in (select v from t);
 v
---
 1
 2
 3
(3 rows)

Is this a bug, or a feature?

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

Re: [sqlite] AUTOINCREMENT documentation.

[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.

[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

[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

[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