[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fossil-users
Subject:    Re: [fossil-users] C API
From:       sky5walk () gmail ! com
Date:       2012-01-08 0:55:21
Message-ID: CAFkD5vux5BeH+XH1vqwHOLvVmv7QpKsWfCKm5_TePDu-HFcTwg () mail ! gmail ! com
[Download RAW message or body]

Ha, I barely have enough time with my own code. :(
Yes, no Stored Procedures, but that's still how I think of fossil and
SQLite together without diving under the hood. ;)
I should have said "SQLite db with lots of C procedures."
Thanks for the edification.

On Sat, Jan 7, 2012 at 7:11 PM, Stephan Beal <sgbeal@googlemail.com> wrote:
> On Sun, Jan 8, 2012 at 12:53 AM, <sky5walk@gmail.com> wrote:
>>
>> Maybe I am being overly simplistic, but I think of fossil as a SQLite
>> database that has stored procedures.
>> Wouldn't it be easier to extend fossil's command set to SQLite's?
>
>
> Yes, that's being over-simplistic :). sqlite3 doesn't support stored
> procedures. It does support adding custom C functions, and fossil makes s=
ome
> (but not extensive) use of that.=A0sqlite3 provides the storage layer, an=
d is
> used to simplify/farm out some of the main logic, but there is a large
> amount of C logic in the app which is essentially independent of sqlite3.
>
> Spend a few hours poking around in the sources and you'll get a better id=
ea
> of what i mean.
>
> --
> ----- stephan beal
> http://wanderinghorse.net/home/stephan/
> http://gplus.to/sgbeal
>
>
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>

[prev in list] [next in list] [prev in thread] [next in thread]