As you suspect, it is straightforward to make a Fortran to SQLite binding.
Here's an example with Fortran 77: http://danial.org/sqlite/fortran/
I don't see why an F95 binding would need to be compiler specific. -- Al
On 4/14/07, Gary Scott <[EMAIL PROTECTED]> wrote:
Hi, this is my first post
Alright thanks! I will look into that.
/Ludvig
On 4/14/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
"Ludvig Strigeus" <[EMAIL PROTECTED]> wrote:
> Does Sqlite support databases larger than 2GB on FAT filesystems?
SQLite supports large databases just fine. It is FAT that does
not support
I followed every one of these threads and it is really good stuff.
I've done some research to realize I need to do more.
I see that most of you are in the client/server world where you can ask
the client various questions about the query.
In my case, I am a standalone server embedded in a devi
Hi, this is my first post, so please excuse any etiquette goofs. I'm
researching incorporation of SQLite into a project. It would appear
relatively straightforward to develop an F95 language binding, however
it is likely to be compiler specific (extensions required to adapt
calling syntax to
"Ludvig Strigeus" <[EMAIL PROTECTED]> wrote:
> Does Sqlite support databases larger than 2GB on FAT filesystems?
SQLite supports large databases just fine. It is FAT that does
not support large files.
>
> If not, how hard would it be to add so it uses additional files for the
> pages that don't
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> In the following pseudo-code which works the first time through either
> Function A or Function B I get a problem when either function is
> executed a second time.
>
> I get the following error:
>
> SQLITE_ERROR[1] - cannot start a transaction with
Marco Bambini <[EMAIL PROTECTED]> wrote:
> I need a way to automatically have the rowid for all queries issued
> by our users (without modifying the original sql queries).
> A lot of time for some queries (COUNT(*) for example), it is simply
> not possible to obtain a valid rowid, so it could j
"dszhang" <[EMAIL PROTECTED]> wrote:
> when i delete some row in my table ... i find the sqlite will free
> some memory that have been free[d] previous[ly].
> my question is why that thing happen and how to solve it?
>
SQLite should never call free() on the same piece of memory
twice. If it does
For all of you who have been wanting to use SQLite3 to manage
authentication on your Apache web servers, I have just released
mod_auth_sqlite3. You may download it from
http://www.lazarusid.com/download/modauthsqlite3-1.0.tar.gz
The module includes both a command line and a web utility for manag
I read this on Sqlite's webpage (http://www.sqlite.org/whentouse.html):
When you start a transaction in SQLite (which happens automatically before
any write operation that is not within an explicit BEGIN...COMMIT) the
engine has to allocate a bitmap of dirty pages in the disk file to help it
mana
10 matches
Mail list logo
