On Mon, Jun 4, 2012 at 10:50 AM, Marco Bambini <ma...@sqlabs.net> wrote:

> I am sorry Dr. Hipp, I am probably doing something wrong,  but I just
> retried and no sessions code is in-line in the final sqlite3.c file.
>
> I downloaded:
>
> http://www.sqlite.org/src/zip/SQLite-d07b7b67d1b3bf65.zip?uuid=d07b7b67d1b3bf65cfe8d96d45a7f1d387bea7ce
>


I'm mistaken.  Session code is in ext/session.  The configure script does
not access it though.  You'll have to do the manually-edited Makefile that
calls main.mk.


>
> then
> cd SQLite-d07b7b67d1b3bf65
> ./configure; make sqlite3.c
>
> preupdate_hook code is in-line but no sessions related code.
> --
> Marco Bambini
> http://www.sqlabs.com
>
>
> On Jun 4, 2012, at 4:38 PM, Richard Hipp wrote:
>
> > On Mon, Jun 4, 2012 at 10:34 AM, Marco Bambini <ma...@sqlabs.net> wrote:
> >
> >> I just tried to download:
> >> http://www.sqlite.org/src/info/d07b7b67d1
> >> from the session branch.
> >>
> >> Then:
> >> ./configure; make sqlite3.c
> >> but no session module is included in the amalgamation sqlite3.c file.
> >>
> >
> > All of the sessions code is in-line in the core.  Enable it using
> > -DSQLITE_ENABLE_PREUPDATE_HOOK -DSQLITE_ENABLE_SESSION.
> >
> >
> >>
> >> From the executed cp command:
> >> cp -f ./src/alter.c ./src/analyze.c ./src/attach.c ./src/auth.c
> >> ./src/backup.c ./src/bitvec.c ./src/btmutex.c ./src/btree.c
> ./src/btree.h
> >> ./src/btreeInt.h ./src/build.c ./src/callback.c ./src/complete.c
> >> ./src/ctime.c ./src/date.c ./src/delete.c ./src/expr.c ./src/fault.c
> >> ./src/fkey.c ./src/func.c ./src/global.c ./src/hash.c ./src/hash.h
> >> ./src/hwtime.h ./src/insert.c ./src/journal.c ./src/legacy.c
> >> ./src/loadext.c ./src/main.c ./src/malloc.c ./src/mem0.c ./src/mem1.c
> >> ./src/mem2.c ./src/mem3.c ./src/mem5.c ./src/memjournal.c ./src/mutex.c
> >> ./src/mutex.h ./src/mutex_noop.c ./src/mutex_os2.c ./src/mutex_unix.c
> >> ./src/mutex_w32.c ./src/notify.c ./src/os.c ./src/os.h ./src/os_common.h
> >> ./src/os_os2.c ./src/os_unix.c ./src/os_win.c ./src/pager.c
> ./src/pager.h
> >> ./src/parse.y ./src/pcache.c ./src/pcache.h ./src/pcache1.c
> ./src/pragma.c
> >> ./src/prepare.c ./src/printf.c ./src/random.c ./src/resolve.c
> >> ./src/rowset.c ./src/select.c ./src/status.c ./src/shell.c ./src/
> >> sqlite.h.in ./src/sqlite3ext.
> >> h ./src/sqliteInt.h ./src/sqliteLimit.h ./src/table.c ./src/tclsqlite.c
> >> ./src/tokenize.c ./src/trigger.c ./src/utf.c ./src/update.c ./src/util.c
> >> ./src/vacuum.c ./src/vdbe.c ./src/vdbe.h ./src/vdbeapi.c ./src/vdbeaux.c
> >> ./src/vdbeblob.c ./src/vdbemem.c ./src/vdbesort.c ./src/vdbetrace.c
> >> ./src/vdbeInt.h ./src/vtab.c ./src/wal.c ./src/wal.h ./src/walker.c
> >> ./src/where.c ./ext/fts1/fts1.c ./ext/fts1/fts1.h ./ext/fts1/fts1_hash.c
> >> ./ext/fts1/fts1_hash.h ./ext/fts1/fts1_porter.c
> ./ext/fts1/fts1_tokenizer.h
> >> ./ext/fts1/fts1_tokenizer1.c ./ext/fts2/fts2.c ./ext/fts2/fts2.h
> >> ./ext/fts2/fts2_hash.c ./ext/fts2/fts2_hash.h ./ext/fts2/fts2_icu.c
> >> ./ext/fts2/fts2_porter.c ./ext/fts2/fts2_tokenizer.h
> >> ./ext/fts2/fts2_tokenizer.c ./ext/fts2/fts2_tokenizer1.c
> ./ext/fts3/fts3.c
> >> ./ext/fts3/fts3.h ./ext/fts3/fts3Int.h ./ext/fts3/fts3_aux.c
> >> ./ext/fts3/fts3_expr.c ./ext/fts3/fts3_hash.c ./ext/fts3/fts3_hash.h
> >> ./ext/fts3/fts3_icu.c ./ext/fts3/fts3_porter.c ./ext/fts3/fts3_snippet.c
> >> ./ext/fts3/fts3_tokeni
> >> zer.h ./ext/fts3/fts3_tokenizer.c ./ext/fts3/fts3_tokenizer1.c
> >> ./ext/fts3/fts3_write.c ./ext/icu/sqliteicu.h ./ext/icu/icu.c
> >> ./ext/rtree/rtree.h ./ext/rtree/rtree.c keywordhash.h opcodes.c
> opcodes.h
> >> parse.c parse.h config.h sqlite3.h tsrc
> >>
> >> no ./ext/session/ folder is included.
> >> Any help?
> >> --
> >> Marco Bambini
> >> http://www.sqlabs.com
> >>
> >>
> >> On May 31, 2012, at 9:27 PM, Richard Hipp wrote:
> >>
> >>> On Thu, May 31, 2012 at 2:55 PM, Charles Samuels <char...@cariden.com
> >>> wrote:
> >>>
> >>> If you are on the sessions branch, then you have the changes just do:
> >>>
> >>> ./configure; make sqlite3.c
> >>>
> >>> Then compile your application with -DSQLITE_ENABLE_SESSION to get the
> >>> functionality.  Documentation on the session extensions is thin but can
> >> be
> >>> seen here:  http://www.sqlite.org/sessions/session.html
> >> _______________________________________________
> >> sqlite-users mailing list
> >> sqlite-users@sqlite.org
> >> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
> >>
> >
> >
> >
> > --
> > D. Richard Hipp
> > d...@sqlite.org
> > _______________________________________________
> > sqlite-users mailing list
> > sqlite-users@sqlite.org
> > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>



-- 
D. Richard Hipp
d...@sqlite.org
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to