Hello Yaron
Ya know I was only trying to give some feedback about the extension.
I identified a user-level issue, suggested a solution
... eliminate the (redundant and non-conforming) parameter-name "_table="
that's my 2 cents.. cheers! /john
On 3/31/2015 3:06 PM, Yaron Koren wrote:
Hi,
I don't
Hi,
I don't know what you mean by the vertical bar thing. Again, most MediaWiki
parser functions take either the form:
{{#function_name:a|b|c}}
...or:
{{#function_name:a=b|c=d|e=f}}
#cargo_declare takes the latter form; and the parameters can actually go in
any order.
-Yaron
On Tue, Mar 31,
Hi Yaron,
To the user, 'field_x' looks and acts like a named parameter.
And to the user, _table is even more so a named parameter, as it is
predefined by the extension.
But to the user, this _table parameter appears to be missing a vertical-bar.
And of course a vertical-bar *can* precede that na
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 McClur
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
Actually, #cargo_declare follows the standard syntax for MediaWiki parser
functions - usually, either all the parameters are named, or none of them
are. #ask is an exception, and #subobject is the very rare exception where
the first parameter is often blank (i.e., your last example).
-Yaron
On Tu
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 th
The first parameter in the following syntax seems error-prone.
{{#cargo_declare:
_table=table name
|field 1=field description 1
|field 2=field description 2
...etc.
}}
Normally mediawiki parser functions are either
{#cargo_declare: table name
|field 1=field description 1
|field 2=field descripti
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 tem
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 wrote:
> Hi John,
>
> How does the absence o
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 na
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 Mc
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__" (?)
Al
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
---
14 matches
Mail list logo
