https://www.sqlite.org/custombuild.html
https://www.sqlite.org/vfs.html
śr., 26 cze 2019 o 08:34 napisał(a):
> Dear SQLite Team,
>
>
>
> I am very new to SQLite and want to use SQLite in my project which is based
> on ARM Cortex M7 core. Do we have any examples available for porting SQLite
> to
> On Jun 25, 2019, at 11:34 PM, vi...@ngxtech.com wrote:
>
> I am very new to SQLite and want to use SQLite in my project which is based
> on ARM Cortex M7 core. Do we have any examples available for porting SQLite
> to cortex M series microcontroller??
It’s written in highly portable C, so jus
Try commenting-out the three lines and
https://www.sqlite.org/src/artifact/e384cb73f?ln=77-79 and see if that
helps. Let us know either way.
On 7/13/17, LukasOsswald wrote:
> Hello,
>
> I am trying to port SQLite3 to an embedded system using an ARM926 running a
> real time os. The VFS is based o
this contains a very basic vfs implementation; kinda uses internal file
abstraction stuff so a lot can be stripped out and replaced with
fopen/fread/etc...
https://code.google.com/p/c-system-abstraction-component-gui/source/browse/src/sqlite/sqlite_interface.c
maybe it's more cryptic than I think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/10/2015 07:03 PM, Jay Kreibich wrote:
> ... VFS is unlikely to make the cut. ... similar things about the
> xBestIndex() and xFilter() functions
I haven't read the book, but one thing that may help is not using C
for these. I think it is easier
On Feb 10, 2015, at 11:21 AM, Peter Aronson wrote:
> You could add VFS creation if you ever do a revised edition (along with a
> virtual table example that actually used xBestIndex and xFilter…)
Given that the book is over four years old and covers to the end of SQLIte3
3.6.x, there are a
On 02/11/2015 12:31 AM, Simon Slavin wrote:
On 10 Feb 2015, at 5:01pm, Clemens Ladisch wrote:
Janke, Julian wrote:
In my opinion, this means, we must ""only"" write a VFS implementation for
our target platform.
What file API is there?
It looks like a standard POXIS implementation. My guess
On 2/10/15, Janke, Julian wrote:
> >
> I know there are two implementations for unix and windows systems in
> os_unix.c and os_win.c,
> but these are very large files, which are not very helpful for a first
> rough
> understanding.
>
See also: https://www.sqlite.org/src/artifact/0396f220561f
--
On 10 Feb 2015, at 5:01pm, Clemens Ladisch wrote:
> Janke, Julian wrote:
>> In my opinion, this means, we must ""only"" write a VFS implementation for
>> our target platform.
>
> What file API is there?
It looks like a standard POXIS implementation. My guess is that the best place
to start w
You could add VFS creation if you ever do a revised edition (along with a
virtual table example that actually used xBestIndex and xFilter...).
On Tuesday, February 10, 2015 9:58 AM, Jay Kreibich wrote:
>
>
>
>
>No, it does not. Using SQLite covers Virtual Tables in great detail, but not
>V
Janke, Julian wrote:
> In my opinion, this means, we must ""only"" write a VFS implementation for
> our target platform.
What file API is there?
Regards,
Clemens
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailm
On Tue, Feb 10, 2015 at 5:58 PM, Jay Kreibich wrote:
> No, it does not. Using SQLite covers Virtual Tables in great detail, but
> not VFS systems. They’re somewhat unusual, after all.
>
My apologies - i mixed my terminology there!
--
- stephan beal
http://wanderinghorse.net/home/stephan/
No, it does not. Using SQLite covers Virtual Tables in great detail, but not
VFS systems. They’re somewhat unusual, after all.
I assume you’ve read the VFS docs: http://www.sqlite.org/vfs.html
>From there, my suggestion is to look closely at the code for the VFS structure
>(http://www.sqlit
On Tue, Feb 10, 2015 at 5:27 PM, Janke, Julian
wrote:
> So my question is, if there is any additional information, how to write a
> VFS?
> Or does anyone have a clue how to start best?
>
This book:
http://www.amazon.de/Using-SQLite-Jay-Kreibich-ebook/dp/B008IGK5QM/
resp.
http://shop.oreilly.
On Wed, Jul 2, 2014 at 2:41 PM, Clemens Ladisch wrote:
> > |Prototype causes non-standard conversion from `int' to
> `sqlite3_int64'
>
> This is just an overzealous and absurdly useless warning.
> Try to reduce the warning level.
>
AFAIK, any conversion from a less precise type to a more pre
Paulo Roberto wrote:
> I'm trying to port SQLite (3.08.04.03) to the Nurit 8400 POS device that
> has an ARM 7 processor and is running Nurit OS 7.50.13a
>
> The error appears when the compiler is building the sqlite.c file (the same
> flags are used).
> |Prototype causes non-standard conversi
On Wed, 2 Jul 2014 12:02:01 +0100, Simon Slavin
wrote:
>
> Thank you for your precise and useful description of what is happening.
>
> Unfortunately this list does not allow attachments, but can you paste
> a copy of the final error, the one about the register map,
> to one of your posts ? Make
On 1 Jul 2014, at 10:32pm, Paulo Roberto wrote:
> There are a lot of warnings due to data type conversion and in the end an
> error relative to register map that I didn't understand.
>
> I would appreciate any help to solve this issue and build it correctly.
>
> The compiler used is an hcarm 4
http://pubs.opengroup.org/onlinepubs/7908799/xsh/systime.h.html
http://pubs.opengroup.org/onlinepubs/7908799/xsh/flockfile.html
http://pubs.opengroup.org/onlinepubs/009695399/functions/fcntl.html
// IEEE Std 1003.1, 2004 Edition @!!= linux
On Tue, May 13, 2014 at 7:55 AM, Artur Deterer wrote:
Geoff,
Did you manage to get sqlite working with MQX?
-- Jay
--
View this message in context:
http://sqlite.1065341.n5.nabble.com/Porting-Sqlite-to-MQX-Operating-system-tp16685p69428.html
Sent from the SQLite mailing list archive at Nabble.com.
___
s
On Thu, Apr 25, 2013 at 7:38 AM, arun.pradeep wrote:
>
> Hi Geoff
>
> I am currently working on porting of SQLITE to MQX RTOS in MPC5125
> Platform.
>
> I am trying to rewrite the sqlite_os_init() for MQX and I have taken Win32
> VFS implementation as the reference.
>
Have you considered using
Hi Geoff
I am currently working on porting of SQLITE to MQX RTOS in MPC5125
Platform.
I am trying to rewrite the sqlite_os_init() for MQX and I have taken Win32
VFS implementation as the reference.
But I am not able to map all of the Win32 file system calls with that of MQX
functions.
Pleas
Hi Geoff
I am currently working on porting of SQLITE to MQX RTOS in MPC5125
Platform.
I am trying to rewrite the sqlite_os_init() for MQX and I have taken Win32
VFS implementation as the reference.
But I am not able to map all of the Win32 file system calls with that of MQX
functions.
Pleas
C Lindgren writes:
> $sql=$db->exec("INSERT INTO users(ID,username,password)
> VALUES
> ('0','".$username."','".$password."')");
In MYSQL, null and 0 are magic for a INTEGER PRIMARY KEY
AUTO_INCREMENT column.
In SQLite,
Quoting Stephan Beal :
On Wed, Oct 5, 2011 at 6:56 PM, C Lindgren wrote:
if (isset ($_post ['submit'] )) {
Aside from this use of POST being a huge security hole, $_post is spelled
wrong: it whould be $_POST (or $_REQUEST if you want to treat GET/POST the
same).
$
On 5 Oct 2011, at 5:56pm, C Lindgren wrote:
> I'm trying to port a simple logon script that was originally for MySQL to
> SQLite3.
MySQL uses connections to a server with a password. SQLite accesses a file on
a hard disk. Make sure your web app (probably apache or httpd) has enough
access
On Wed, Oct 5, 2011 at 6:56 PM, C Lindgren wrote:
> if (isset ($_post ['submit'] )) {
Aside from this use of POST being a huge security hole, $_post is spelled
wrong: it whould be $_POST (or $_REQUEST if you want to treat GET/POST the
same).
>$sql=$db->exec("INSERT INT
Geoff,
I know this is an old post, but I am investigating designs for a project
that might benefit from Sqlite support on MQX. In your initial post you
mentioned posting your results. Were you ever able to get this working?
Thanks,
Sean
--
View this message in context:
http://old.nabble.com
Thanks. I took a guess that it was fixed in 3.7.3 and manually downloaded
the source. Of course hitting refresh in my browser brought up the
correct page. PEBKAC.
-Scott
sqlite-users-boun...@sqlite.org wrote on 10/11/2010 04:04:32 PM:
> See:
>
> http://www.sqlite.org/src/info/d1ed743b6e
>
See:
http://www.sqlite.org/src/info/d1ed743b6e
for changes for SQLITE_OMIT_WAL.
3.7.3 should be available from the downloads page:
http://www.sqlite.org/download.html
as of October 8, 2010. You might need to refresh your browser cache.
Direct link to the amalgamation is:
http://www.sqlite.o
I think there is a bug in 3.7.2 when you define SQLITE_OMIT_WAL. There
are references to pagerPagecount() that cannot be resolved because that
function is defined inside of a #ifndef SQLITE_OMIT_WAL.
I also keep seeing references to 3.7.3 in this list. But the SQLite
download page only has li
I am a little reluctant to modify our kernel configuration. Primarily out
of ignorance because I know very little about vxWorks.
Do you happen to know if these functions are used by the new WAL logic?
I'm assuming by the names that they could be related to memory mapped
files. What switches
Hello Scott,
I did some searching with these symbols, they should be in 'libos.a'.
rtpLib.o - rtpVerifyAndLock
pgMgrLib.o - pgMgrPageFree, pgMgrPageAllocAt
you should modify kernel components with your VIP project.
Best Regards,
Huang ZhiHua
2010/10/9 Scott A Mintz
> Thank you. Th
Thank you. Those changes (modified slightly for 3.7.2) allowed me to
create a DKM project that compiles sqlite3.c to libSQLite3.a.
However, when I link my main VIP project, I get the following unresolved
errors:
dld: warning: Undefined symbol 'rtpVerifyAndLock' in file 'partialImage.o'
dld: war
Hello Scott,
Below is my patch on the latest SQLite 3.7.3. Please notice that I only
verify it with GCC 4.1.2 compiler in VxWorks 6.6/6.7/6.8(I have not verify
it with my real target machine yet).
*** sqlite3.c.orig2010-10-08 10:42:22.0 +0800
--- sqlite3.c2010-10-08 19:24:18.3
If task 1 will have only one connection to customer.db and task 2 will
have only one connection to fault.db then it looks like you don't need
any locking indeed. And most part of mutexes is not necessary too,
although probably you'll need ones that protect some global variables
(can't say how many
Hello Dan
>Do the tasks share a heap? And do you have multiple connections
>to the database (multiple calls to sqlite3_open() or sqlite3_open_v2().
I would like to keep the implementation as general purpose as possible so we
can use sqlite in the future in differient Applications. Therefore I w
On Mar 16, 2010, at 5:22 AM, GeoffW wrote:
>
> Hello Dan
>
> Thanks for your useful input. To answer your questions.
>
>> Do you have any file-locking primitives provided by the OS?
> There are no file locking OS Primitives at all that I can use.
>
>> Do you have clients connecting to the databas
Hello Dan
Thanks for your useful input. To answer your questions.
>Do you have any file-locking primitives provided by the OS?
There are no file locking OS Primitives at all that I can use.
>Do you have clients connecting to the database from multiple
>processes? Or only multiple threads within
On Mar 15, 2010, at 10:04 PM, GeoffW wrote:
>
> Hi Kees
>
> Thanks for the response and giving me a clue to look at dot locking,
> I had
> missed the dot lock mechanism as I had concentrated mainly on the
> osWin.c
> file. I cant find any documentation other than the source code on
> how th
Hi Kees
Thanks for the response and giving me a clue to look at dot locking, I had
missed the dot lock mechanism as I had concentrated mainly on the osWin.c
file. I cant find any documentation other than the source code on how this
low level file locking stuff is implemented.
I am currently read
On Fri, 12 Mar 2010 02:22:31 -0800 (PST), GeoffW
wrote:
>
>Hi
>
>Now I have got a half ported version of Sqlite up and running on MQX I cant
>put off any longer the question of file locking and how I tackle that ? For
>the moment i had made the xLock() and xUnlock() the same as in osWin.c
>versio
hello
I thought I had better update this and confess to my sins. Good job no one
is reading this thread as it is an embarassingly stupid mistake :rules:
I cant believe I did this and then took so long to spot it.
int sqlite3_os_init(void)
{
static sqlite3_vfs mqxVfs = {
1,
Hi
I wasted another entire day on this without really being able to grasp what
the problem is.
The call sequence is for the sqlite3OsClose() function
Working Windows version
pager_unlock() pPager->jfpd where pMethods =0
releaseAllSavepoints() pPager->sjfpd where pMethods =0
above 2 lines repe
hello Dan
Thanks for the very speedy reply. I have just been experimenting with the
working Windows version.
I only get one hit of the winOpen() function and that is with a filename
parameter of the full path to my test.db file
So maybe it is not a temporary journal file or maybe I am misunder
>
> http://old.nabble.com/file/p27792715/stack.jpg
>
> I know its a long shot but does Dr Hipp or anyone have any possible
> ideas
> what could give rise to a premature file close ? Sorry my message
> was so
> long. Thanks for any ideas
SQLite thinks it is closing the statement journal here,
Jay A. Kreibich wrote:
> On Wed, May 07, 2008 at 10:25:49PM -0400, Andrew Cunningham scratched on the
> wall:
>
>
>> "I have doubts that you will be able to get SQLite to work on anything
>> less than a 32-bit processor.
>> D. Richard Hipp"
>>
>
>
>> I was under the impression as long a
On Wed, May 07, 2008 at 10:25:49PM -0400, Andrew Cunningham scratched on the
wall:
> "I have doubts that you will be able to get SQLite to work on anything
> less than a 32-bit processor.
> D. Richard Hipp"
> I was under the impression as long as the processor had enough room to
> hold the progr
*snip*
"I have doubts that you will be able to get SQLite to work on anything
less than a 32-bit processor.
D. Richard Hipp"
I was under the impression as long as the processor had enough room to
hold the program (and RAM) it would work. The difference I would have
expected would simply be speed
At 02:43 07/05/2008, you wrote:
>Hi,
>
>I was wondering if anyone has any basic guide lines on embedding SQLite into
>a microcontroller. For example, I am considering using an 8/16 bit processor
>with 1 MB flash, 1 MB SRAM and 2 GB data storage (SD card). Has anyone ported
>this before to an emb
On May 6, 2008, at 8:43 PM, Andrew Cunningham wrote:
> Hi,
>
> I was wondering if anyone has any basic guide lines on embedding
> SQLite into
> a microcontroller. For example, I am considering using an 8/16 bit
> processor
> with 1 MB flash, 1 MB SRAM and 2 GB data storage (SD card). Has
thank you for your reply.
I have make it run on our embeded os and make some simple tests. it runs
ok.
great!!
"Nuno Lucas" <[EMAIL PROTECTED]>
2007-05-12 07:03
Please respond to
sqlite-users@sqlite.org
To
sqlite-users@sqlite.org
cc
Subject
Re: [sqlite] porting sqlit
On 5/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I am porting sqlite3 to the embeded os,such as threadx,nucleus,ect..
I am writing the file such as os_threadx.c,os_nucleus.c according to the
os_win.c,os_unix.c.
I have read the os_win.c and find that there is a switcher OS_WINCE in the
stru
...
Best regards,
Fred
- Message d'origine
De : [EMAIL PROTECTED]
À : sqlite-users@sqlite.org; Fred a <[EMAIL PROTECTED]>
Envoyé le : Dimanche, 21 Mai 2006, 8h09mn 57s
Objet : Re: [sqlite] Porting sqlite3 library problems
Fred a <[EMAIL PROTECTED]> wrote:
> Hel
Fred a <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> I port successfully sqlite3 library on other platform...
> But i have some problems...
>
> When i try to insert some records, if for example i insert
> 80: good; if i try to insert 81 records the database is corrupted
This suggests to me
On 5/21/06, Fred a <[EMAIL PROTECTED]> wrote:
Hello all,
I port successfully sqlite3 library on other platform...
But i have some problems...
When i try to insert some records, if for example i insert 80: good; if i try
to insert 81 records the database is corrupted
I don t understand
I gave up on this port. Far more complicated than what I initially thought.
Guess I'll have to implement stupid flat files manually. :((
On 12/30/05, Jay Sprenkle <[EMAIL PROTECTED]> wrote:
> Yes, most people load the data to persistant memory when shutting
> down, or periodically
> to save a
Yes, most people load the data to persistant memory when shutting
down, or periodically
to save a snapshot, and load it when booting up. It's fast but if your hardware
can't detect a power failure and write the data with what power
remains in the power supply
capacitors you risk losing some data in
be used for seldom changed tables or config parameters.
> >
> > Otherwise I am limited to the battery backed up RAM-based file system.
> >
> >
> >
> > -Original Message-
> > From: Jay Sprenkle [mailto:[EMAIL PROTECTED]
> > Sent: Jueves, 29 de Di
005 12:10 p.m.
> To: [EMAIL PROTECTED]
> Subject: Re: [sqlite] Porting SQL to run on a proprietary operating system
>
> I did a project using sqlite under web server CGI. It worked very well and
> was pretty light on required resources. My guess is this will work for you
> as well
: Re: [sqlite] Porting SQL to run on a proprietary operating system
I did a project using sqlite under web server CGI. It worked very well and
was pretty light on required resources. My guess is this will work for you
as well but you'll need to research some changes to the database engine to
On Wed, 14 Sep 2005, Jay Siegel wrote:
>I'm on my second day of porting SQLite to an embedded
>environment. I'm not sure if this is the appropriate
>place to put these comments about the experience.
>I've seen some type of "ticket" mechanism in CVS but I
>don't know if these comments raise to the
On Wed, 2005-09-14 at 11:55 -0700, Jay Siegel wrote:
> I turned on almost all of the OMIT definitions
> since size is very important on my embedded platform.
> This causes a few problems with definitions in
> parse.c. This is documented somewhere and I expected
> it. It shouldn't be necessary to
On 9/14/05, Jay Siegel <[EMAIL PROTECTED]> wrote:
>
> The porting effort has now turned to a testing
> effort...
Don't forget there are a lot of regression test cases provided with the
source.
---
The Castles of Dereth Calendar: a tour of the art and architecture of
Asheron's Call
http://ww
Never mind, the native compiler DOES support 64-bit integers :-)
David,
It looks like LockRecord does what you'd want to get this port done. If
a single-threaded port is all you want you can probably use the logic in
the os_win.c file.
The difference in the Win32 and Posix models are the following:
Win32: locks are held by file handles
Posix: locks are held
Thanks for responding Gé
There are the usual options of buffered and unbuffered file i/o in AmigaOS.
A given file can be opened either in a shared mode, or an exclusive mode by
a process, but it can also be locked first and then opened. It cannot be
locked individually for a given pthread runnin
David Pitcher wrote:
> The claim that it works over a networked drive has made me
> start to think that operating system specific locking mechanisms are totally
> the wrong way to go, and that I have misunderstood the code.
OS locking mechanisms are supposed to work over a network.
>[...] or s
Dave,
The os_unix.c locking code is extremely convoluted because of the rather
insane Posix locking semantics, which tend to make writing threaded code
excessively complicated, e.g. if two threads are accessing the same file
and one thread closes its file handle the other thread loses all its lock
69 matches
Mail list logo
