A less LMGTFY-like response:
First off, using SQLite does require that you become familiar with SQL, and a
bunch of database ideas: normalization for good schema design, unit of work for
good use of transactions, how to use indexes, others I'm sure I don't know
about. But those ideas are not specific to SQLite, and are good to think about
anyway. And any part of SQL or db design you learn will be far easier than
trying to deal with the same problems in a file format you've written yourself.
If you want to use SQLite in a c/c++ app, your easiest option is to simply
download the amalgamation and include it in your project. That's two files -
SQLite.c and SQLite.h. The basic procedure is:
Open the file: sqlite3_open(...);
prepare your statement: sqlite3_prepare_v2(...);
Bind your parameters: sqlite3_bind(...);
In a loop {
execute the statement: sqlite3_step(...);
Retrieve data if it's a select: sqlite3_column(...);
}
Finalize or reset the statement (depending if you want to use it again):
sqlite3_finalise / sqlite3_reset
Close the file: sqlite3_close(...)
If you're using dotNet, you can use NuGet to install system.data.sqlite.core,
then #using system.data.sqlite you'll find a ado.net database interface which
you should more or less use like any other ado.net db interface (with the
advantage that if you ever migrate to another dbms will be easier).
I can't comment on Python, I haven't used that.
I never thought SQLite difficult to start using. In fact, possibly what I
didn't want to accept at first was exactly how easy it was and thought there
were things I was missing*.
For all but the simplest use cases I think SQLite is far easier than direct
file access for the fact that it keeps track of the contents of the file for
you, you have an extensible self documenting file format (in the form of your
db schema), and it takes care of most of your robustness concerns by making
everything ACID.
* there were things I was missing - like getting all the config right, and
making sure to reset or finalize statements, and making sure to always do any
file operations on the log file(s) too. But even with these mistakes it still
worked leagues better than anything I could have written myself, with a
fraction of the work.
> On 5 Mar 2017, at 9:20 PM, Jens Alfke <j...@mooseyard.com> wrote:
>
>
>> On Mar 5, 2017, at 3:03 AM, NTrewartha T-Online <ntrewar...@t-online.de>
>> wrote:
>>
>> Any examples of a C,C++,C# or Python usage for sqllite.?
>
> Have you tried searching? I entered “sqlite c example” and “sqlite python
> example” into Google and got some useful-looking links in the top few hits.
> Also, there are quite a few books about SQLite.
>
>> I would like sqllite on my raspberry pi 3 after I have gained experience
>> under Windows 10.
>
> If it’s not installed already in the Raspbian OS, you should just need to run
> “sudo apt-get sqlite”. (Possibly “sudo apt-get sqlite_dev” since IIRC the
> development resources like header files are in separate packages under
> Debian-based distros.)
>
>> Judging what the replies to questions, the very new beginners are left a bit
>> out in the cold.
>
> No offense intended, but SQLite isn’t an especially beginner-friendly tool.
> It’s a powerful relational database with a ton of configurable options, and a
> somewhat tricky C API, not to mention a sophisticated query language that you
> also need to master to make effective use of it. (However, using it from
> Python should be somewhat easier, since the API is a bit higher level and you
> don’t have to worry about things like memory management.)
>
> If your data storage needs aren’t too complex, there are simpler ways to
> implement it. For example, in the past I’ve just used a simple data
> serialization library to read and write the entire data set to disk. It works
> great when the data is small enough that it fits easily in memory and doesn’t
> take too long to read or write (say, under 100MB.) This is the equivalent of
> using a regular battery-powered drill to make some holes, instead of learning
> how to use a router or end mill :)
>
> (Also, in general if you’re moving from Windows to literally any other
> platform, you’ll have to re-learn some of your development processes. Windows
> does things differently from Unix, which is what everything else is based on.)
>
> —Jens
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
