From: John M. <jmc...@hy...> - 2015-03-31 17:17:36
|
Hi Yaron I am unable to use Cargo in wikifarms (or with prefixed tables of any sort for that matter) It appears $wgDBprefix is not used in Cargo code, rather it uses its own prefix "Cargo__" (?) Also plz do not prevent table names with leading underscores. thanks/john |
From: John M. <jmc...@hy...> - 2015-03-31 17:31:13
|
Curious why cargo_declare must be in a template? thanks On 3/31/2015 10:17 AM, John McClure wrote: > Hi Yaron > I am unable to use Cargo in wikifarms (or with prefixed tables of any > sort for that matter) > It appears $wgDBprefix is not used in Cargo code, rather it uses its own > prefix "Cargo__" (?) > Also plz do not prevent table names with leading underscores. > thanks/john > > ------------------------------------------------------------------------------ > 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 > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-devel -- thanks/john skype:hypergrove |
From: Yaron K. <ya...@wi...> - 2015-03-31 17:47:47
|
Hi John, How does the absence of the main MediaWiki DB prefix affect the running of the wiki farm - are you using one database for all the wikis, with a different table prefix for each? And why do you want leading underscores in Cargo table names? -Yaron On Tue, Mar 31, 2015 at 1:17 PM, John McClure <jmc...@hy...> wrote: > Hi Yaron > I am unable to use Cargo in wikifarms (or with prefixed tables of any sort > for that matter) > It appears $wgDBprefix is not used in Cargo code, rather it uses its own > prefix "Cargo__" (?) > Also plz do not prevent table names with leading underscores. > thanks/john > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com |
From: John M. <jmc...@hy...> - 2015-03-31 17:59:41
|
On 3/31/2015 10:47 AM, Yaron Koren wrote: > Hi John, > > How does the absence of the main MediaWiki DB prefix affect the > running of the wiki farm - are you using one database for all the > wikis, with a different table prefix for each? yes > > And why do you want leading underscores in Cargo table names? because I do. > > -Yaron > > On Tue, Mar 31, 2015 at 1:17 PM, John McClure <jmc...@hy... > <mailto:jmc...@hy...>> wrote: > > Hi Yaron > I am unable to use Cargo in wikifarms (or with prefixed tables of > any sort for that matter) > It appears $wgDBprefix is not used in Cargo code, rather it uses > its own prefix "Cargo__" (?) > Also plz do not prevent table names with leading underscores. > thanks/john > > > > > -- > WikiWorks · MediaWiki Consulting · http://wikiworks.com -- thanks/john skype:hypergrove |
From: Yaron K. <ya...@wi...> - 2015-03-31 18:00:27
|
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. On Tue, Mar 31, 2015 at 1:47 PM, Yaron Koren <ya...@wi...> wrote: > Hi John, > > How does the absence of the main MediaWiki DB prefix affect the running of > the wiki farm - are you using one database for all the wikis, with a > different table prefix for each? > > And why do you want leading underscores in Cargo table names? > > -Yaron > > On Tue, Mar 31, 2015 at 1:17 PM, John McClure <jmc...@hy...> > wrote: > >> Hi Yaron >> I am unable to use Cargo in wikifarms (or with prefixed tables of any >> sort for that matter) >> It appears $wgDBprefix is not used in Cargo code, rather it uses its own >> prefix "Cargo__" (?) >> Also plz do not prevent table names with leading underscores. >> thanks/john >> > > > > -- > WikiWorks · MediaWiki Consulting · http://wikiworks.com > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com |
From: John M. <jmc...@hy...> - 2015-03-31 18:06:32
|
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 |
From: Yaron K. <ya...@wi...> - 2015-03-31 19:43:21
|
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__". 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. On Tue, Mar 31, 2015 at 2:06 PM, John McClure <jmc...@hy...> 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 |
From: John M. <jmc...@hy...> - 2015-03-31 19:54:53
|
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 <jmc...@hy... > <mailto:jmc...@hy...>> 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 |
From: John M. <jmc...@hy...> - 2015-03-31 21:21:31
|
Ok, thanks for making the change for $wgDBprefix -- tested out okay. I hope you decide to allow cargo_declare to be on a page that is not a template. - separates declaration from use, a good thing to do On 3/31/2015 1:09 PM, Yaron Koren wrote: > Hi, > > On Tue, Mar 31, 2015 at 3:54 PM, John McClure <jmc...@hy... > <mailto:jmc...@hy...>> wrote: > > > > 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? > > > Oh, now I understand the confusion. Cargo has two predefined tables > (cargo_tables and cargo_pages), and then creates additional tables, as > needed, for the actual user data. It's these additional tables that > have the "cargo__" prefix, with two underscores. > > >> >> 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. > > > I suppose you could do that, yes. > > -Yaron > >> >> On Tue, Mar 31, 2015 at 2:06 PM, John McClure >> <jmc...@hy... <mailto:jmc...@hy...>> 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. >>> |