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

List:       fossil-dev
Subject:    [fossil-dev] looking for code which joins tables across checkout and repo?
From:       Stephan Beal <sgbeal () googlemail ! com>
Date:       2013-09-09 15:24:09
Message-ID: CAKd4nAgmB=KLoffUqLsZG0Qpt=wyFm5snfk0VXf7xFSkz_fRBg () mail ! gmail ! com
[Download RAW message or body]

Hi, all,

i'm looking for some SQL code in fossil which joins across both the repo an
checkout dbs. So far i have found none, but figure you guys might be able
to name some off the tops of your heads.

:-?

The reason: in libfossil i'm currently handling the db handle much like
f(1) does it: whichever db is opened first becomes the "main" db. As other
dbs are opened, they get attached to the main db. Typically the checkout
will be the main db and then its repo gets attached (but it's of course
possible to open a repo without a checkout). So far libf doesn't do
anything with the config db (because all the config options stored there
are app-level). i'm contemplating splitting the dbs into separate handles
(as i had originally done), but i can't do that if the checkout and repo
need to join tables at some point.

-- 
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal

[Attachment #3 (text/html)]

<div dir="ltr">Hi, all,<div><br></div><div>i&#39;m looking for some SQL code in \
fossil which joins across both the repo an checkout dbs. So far i have found none, \
but figure you guys might be able to name some off the tops of your heads.</div> \
<div><br></div><div>:-?</div><div><br></div><div>The reason: in libfossil i&#39;m \
currently handling the db handle much like f(1) does it: whichever db is opened first \
becomes the &quot;main&quot; db. As other dbs are opened, they get attached to the \
main db. Typically the checkout will be the main db and then its repo gets attached \
(but it&#39;s of course possible to open a repo without a checkout). So far libf \
doesn&#39;t do anything with the config db (because all the config options stored \
there are app-level). i&#39;m contemplating splitting the dbs into separate handles \
(as i had originally done), but i can&#39;t do that if the checkout and repo need to \
join tables at some point.</div> <div><div><br></div>-- <br>----- stephan beal<br><a \
href="http://wanderinghorse.net/home/stephan/" \
target="_blank">http://wanderinghorse.net/home/stephan/</a><div><a \
href="http://gplus.to/sgbeal" target="_blank">http://gplus.to/sgbeal</a></div>

</div></div>



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