1

Topic: QT and SQLite

. Input: There is certain a software written on QT and using as DB SQLite. I have an aaplet which uses this basis independently and builds reports. Here suddenly to software developers was impatient to cipher a DB using such project as Sqlcipher the Essence is that, the code for operation from a DB remains same, to change generally it is necessary nothing. The only thing that needs to be made - right after discoveries to fulfill such SQL request "PRAGMA key = ' password ';" And everything, the basis will be ciphered by the automatic machine, is transparent for the user or is opened already . Two days I killed trying to understand as to collect library sqlcipher. I hate! But that is not the question, in general at last gathered necessary dll, and the password from basis to me informed. I it's done thought, but not here that was. I add in the application this  instead of normal sqlite - the DB refuses to open. At first thought that  with the assembly  and it does not work. Outlined test application - all norms, works normally with new basis both in  a type and in the normal. That basis from a software refuses to open. Questions: Who is guilty? How much I had time to study question QT - drivers for each DB there are used. But besides how much I understood, they gather from standard source codes. Cannot Sqlcipher collected separately to work not how collected in the form of the driver of a DB for QT? Judging by , the normal library at first gathers, and from it the driver for QT becomes. The second variant, probably software developers made any changes to code Sqlcipher, and now their basis a horse-radish will open by means of independently assembled library. What to do? While to me the idea came to a head to rewrite the  on QT, and to use those files of drivers of the DB, going complete with a software. Likely it gives 100 % a warranty of normal operation from a DB. Truth here is an ambush, I never wrote nothing on QT, I am afraid unmaking process can be tightened. It would be desirable to listen to your reasons on all this situation. And more specific question - if is already  the driver of a DB for QT, it is simple in the code all is connected also? Or it is necessary for the project somehow it is all ?

2

Re: QT and SQLite

Hello, Evgeniy Skvortsov, you wrote: ES> Outlined test application - all norms, works normally with new basis both in  a type and in the normal. ES> that basis from a software refuses to open. ES> how much I had time to study question QT - drivers for each DB there are used. Not mandatory, from QT it is possible to pull API any engine directly if there is an appropriate library from the developer of a DB. ES> the second variant, probably software developers made any changes to code Sqlcipher, and now their basis a horse-radish will open by means of independently assembled library. ES> what to do? Something I looked sqlcipher, there in by means of PRAGMA it is possible not only key to set, but also a method of encoding and a heap of other parameters.  a debugger the software about sequence of commands of the DB, causes which software at DB discovery. If the library gathers as well as used, as dynamic then generally problems are not present, whether easily to be convinced of the password a problem, picking up ready library. As, it is possible also dynamic in this case to palm off, adding the full broad gull of commands of a DB.

3

Re: QT and SQLite

Hello, Maniacal, you wrote: M> Something I looked sqlcipher, there in by means of PRAGMA it is possible not only key to set, but also a method of encoding and a heap of other parameters. A pancake, that I also did not note an elephant! I will look that there still it is caused after  .

4

Re: QT and SQLite

Hello, Maniacal, you wrote: M> Something I looked sqlcipher, there in by means of PRAGMA it is possible not only key to set, but also a method of encoding and a heap of other parameters.  so it would be desirable on simple . But is not present. After a call "pragma key" at once go normal select `  It is necessary to look at assembly parameters , any algorithm by default can there is set.

5

Re: QT and SQLite

Hello, Evgeniy Skvortsov, you wrote: I the IDIOT!!! But the clever idiot! Later 3 days of sufferings to me in a head one clever thought flew, and it works! The pancake, pair  and all works as a mouse! Lines, it was necessary to do nothing, why such elementary decision so was difficultly gave? A brain, a bough, a piece class! I am bloated with happiness! The occasion is. Thanks all answered in this subject and in the adjacent. For a long time wanted to start to understand with Qt, here and the occasion quitted. It appears Qt works from a box. Respect to authors! Delivered MSVC 2010, QT 4.8.1, for studio and all earned at once a plug-in! Without any dancings. Qt the designer works, projects gather, beauty!

6

Re: QT and SQLite

Hello, Evgeniy Skvortsov, you wrote: ES> I the IDIOT!!! ES> but the clever idiot! Well, to you we will not hinder.

7

Re: QT and SQLite

Hello, Qt-Coder, you wrote: QC> Well, to you we will not hinder. Yes is not present, all thanks, but the decision of my problem is simple it appeared much easier, than I could present.

8

Re: QT and SQLite

Hello, Evgeniy Skvortsov, you wrote: ES> Hello, Qt-Coder, you wrote: QC>> Well, to you we will not hinder. ES> yes is not present, all thanks, but the decision of my problem is simple it appeared much easier, than I could present. There was such film Heart Angela, Miki Rourke, there there was character Lui Tsajfer (on a film context it is the Lucifer) so similar it SQL-tsajfer sending to this film

9

Re: QT and SQLite

Hello, loginx, you wrote: L> There was such film Heart Angela, Miki Rourke, there there was character Lui Tsajfer (on a film context it is the Lucifer) the Film class. L> so it is similar SQL-tsajfer sending to this film Cypher is a cipher with . The Word-play, no more.

10

Re: QT and SQLite

Hello, Evgeniy Skvortsov, you wrote: ES> Helou. ES>... All I want to ask, why you so went in cycles in version 4.8.1? There are fresher, with a smaller amount of bugs and supported by newer versions  assembly. And with binary compatibility. Somewhere even saw 4.8.7 collected under 2017 studio.

11

Re: QT and SQLite

Hello, SaZ, you wrote: SaZ> All I want to ask, why you so went in cycles in version 4.8.1? There are fresher, with a smaller amount of bugs and supported by newer versions  assembly. And with binary compatibility. Somewhere even saw 4.8.7 collected under 2017 studio. I think, such can be connected to the restrictions stipulated in .

12

Re: QT and SQLite

Hello, Maniacal, you wrote: M> I Think, such can be connected to the restrictions stipulated in . . Well if you  yes, it is possible to do stupidly as speak. But normally any restrictions justify, though is minimum. In a case with the certain version of the compiler I can understand. There is an iron under which it is difficult to find the fresh compiler. Restriction by version 4 too can be understood (though and it is difficult - on Qt5 other approach to  and presence  the code) can complicate migration. I can even understand version 4.8 usage, I remember at us there was the extremely painful migration with 4.6 on 4.7. But that is why it is necessary 4.8.1 - I do not understand categorically. There only small , in the core for  newer compilers. Which at all does not break binary compatibility: if you enclose to the program written under 4.8.1.dll from 4.8.7 she at all does not note it. And here development becomes simpler.

13

Re: QT and SQLite

Hello, SaZ, you wrote: SaZ> All I want to ask, why you so went in cycles in version 4.8.1? I do not have development experience on Qt, therefore in order to avoid problems took this version, with this version is collected a software working with a DB. As I assumed that it is necessary to use part DLL from this application. And about subtleties did not know.

14

Re: QT and SQLite

Hello, SaZ, you wrote: SaZ> But that is why it is necessary 4.8.1 - I do not understand categorically. For example at code writing under Astra Linux Special Edition the certain version. 4.8.1 there is not present, but in version 1.3, for example, it is rigid Qt 4.8.3 and the components, libraries in system, only that goes in the distribution kit (for safety reasons), etc. is forbidden to put. However, all the same Qt it is possible to collect from the approved SATS of source codes....