On 3/31/2015 12:43 PM, Yaron Koren wrote:
Hi,

Ah, I didn't think about multiple wikis using the same database. I just checked in a fix so that the prefix for Cargo tables is not $wgDBprefix + "cargo__", instead of just "cargo__".
I honestly dont understand where this "cargo__" prefix comes into play.
The two Cargo tables I see in the database are $wgDBprefix.cargo_tables and $wgDBprefix.cargo_pages.
So where does your prefix with a double underscore come into play?

Each template that stores data needs its own #cargo_declare call. If more than one template stores data to the same table (which may be what you're asking about), then one needs #cargo_declare, and the rest need #cargo_attach.
But I'm asking whether your requirement that cargo_declare must be in a template, is really necessary. That is, why can't all templates follow the same pattern: all use cargo_attach.

On Tue, Mar 31, 2015 at 2:06 PM, John McClure <jmccl...@hypergrove.com <mailto:jmccl...@hypergrove.com>> wrote:

    If there are multiple templates that store data, which one does
    the declare go into?
    If any, that is it doesn't matter which, then is this constraint
    you're imposing actually necessary?
    thanks

    On 3/31/2015 11:00 AM, Yaron Koren wrote:
    Oh, I missed your other question - Cargo is built around
    templates; they are responsible for storing data, so it made
    sense to put both the table declaration and the table storage go
    into the template page.


-- thanks/john
    skype:hypergrove




--
WikiWorks · MediaWiki Consulting · http://wikiworks.com

--
thanks/john
skype:hypergrove
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel

Reply via email to