On Thu, Jul 24, 2014 at 4:51 PM, Stephan Beal wrote:
> [stephan@host:~/cvs/fossil/libfossil/src]$ f-query -e "select * from
> ckout.vfile limit 1" -S
>
BTW: the -S option has historically meant "SQL Tracing," but i think i'll
rename it to "Simon" now ;). i've been fighting with this db name jugg
On Thu, Jul 24, 2014 at 4:45 PM, Simon Slavin wrote:
>
> On 24 Jul 2014, at 3:38pm, Stephan Beal wrote:
>
> > THANK YOU!
>
> You're welcome. I'm still learning more from this list than I'm putting
> out.
>
Hope we never meet, because i will likely kiss you if we do:
[stephan@host:~/cvs/fossil
On 24 Jul 2014, at 3:38pm, Stephan Beal wrote:
> THANK YOU!
You're welcome. I'm still learning more from this list than I'm putting out.
Simon.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sql
On Thu, Jul 24, 2014 at 4:10 PM, Simon Slavin wrote:
>
> On 24 Jul 2014, at 3:07pm, Stephan Beal wrote:
>
> > A simpler solution which would serve my goals just as well: the ability
> to
> > rename only 'main' (e.g. sqlite3_rename_db(sqlite3*, char const *
> > newName)). i don't need 'main' beca
On 24 Jul 2014, at 3:07pm, Stephan Beal wrote:
> A simpler solution which would serve my goals just as well: the ability to
> rename only 'main' (e.g. sqlite3_rename_db(sqlite3*, char const *
> newName)). i don't need 'main' because main is fluid in these apps. i need
> a well-defined name which
On Thu, Jul 24, 2014 at 4:02 PM, Simon Slavin wrote:
> Really ? It would dramatically simplify your programming and not take up
> much space. Oh well.
>
It's not the space, but the "pile of files" debate which has raged for
years in SCMs. Fossil already has its one "clutter" file, just like sv
On 24 Jul 2014, at 2:52pm, Stephan Beal wrote:
> note that i can't justify using a file for this purpose, because that file
> has to live somewhere, and the only reasonable place for it is in the
> checkout directory. It would clutter the source trees.
Really ? It would dramatically simplify y
On Thu, Jul 24, 2014 at 3:51 PM, Stephan Beal wrote:
> i did in fact try that (way back in the beginning), using a :memory: db as
> my main db.
>
note that i can't justify using a file for this purpose, because that file
has to live somewhere, and the only reasonable place for it is in the
check
On Thu, Jul 24, 2014 at 3:18 PM, Simon Slavin wrote:
> Create a fourth database with no content. That's always the main one.
> Everything else is always attached to it.
>
i did in fact try that (way back in the beginning), using a :memory: db as
my main db. However, the :memory: VFS is (intere
On 24 Jul 2014, at 2:11pm, Stephan Beal wrote:
> The problem is, an application does not
> (cannot) necessarily know which order the dbs were opened, so it doesn't
> really know if "main" is the repo db, the checkout db, or the config db.
Create a fourth database with no content. That's always
Hi, sqlite team,
i meant to address this directly to Richard a couple weeks back, but we got
carried away with other topics...
In the Fossil SCM and (by extension) libfossil, we juggle 1-3 db handles
for the config, checkout, and repo dbs. The first db which gets opened
(it's use-case dependent!)
11 matches
Mail list logo