You use such a column as a foreign key into another table. the values) are fully qualified page IDs. In order to refer to such a row from another table, you use a column of the type page. Rows in a table which is bound to wiki pages are identified by the ID of the pages. The struct plugin defines one data type within the schema for exactly that purpose. The values in those columns for one Call row would exactly correspond to the values in the primary key of a row in the Persons table, thus identifying the Person who was associated with the Call. In an orthodox relational database, you would define one or more columns in the Calls table as a foreign key. Now you need to associate each row in the Calls table with one row in the Persons table. As far as I can make out, tables of this kind have no primary keys. Its rows do not correspond to any wiki pages. The other table ('Calls') is defined as a so called "Global Data". the namespace(s) followed by the page name. Actually, the primary key for each row is simply the fully qualified Id of the page associated with that row, i.e. The primary key for this table ('ID') is provided by the struct plugin and is not explicitly visible in its schema. In my sketch #1 above, each row of the Person (or Customer) table is associated with one wiki page. The database contains exactly two schemas, corresponding, of course, to two tables. I think some of your difficulty lies with trying to understand the struct plugin within the mindset of the underlying database. Jpr105 Would be interesting if I can fix this join problem. It is not there to disregard the contribution of completeness:Ī person.csv "pid","code","first name","last name" Actually, I just wanted to see if it worked. Struct_fieldhidden "call.person_code" "call.person_name" "call.person_page" "Save call" Struct_field "call.initiales" "call.date" =%Y-%m-%d Page Call History: = Call History =Īnd one of the Person Page: = Max Mustermann = Page Overview: = Search for Customer =Ĭols: %pageid%, code, first name, last name There are two schemas (very basic in the example): I had a little bit time before holliday □ When the company had all different option of monthly fee vs commission rate.Ok, after the nice post from i have also created a sample for Struct. The best advice i could give you is use a comission per sale route approx! I did this a few years back selling electricity and gas contracts in the uk! I plan on only using excel to keep track / time as i will be providing the database to them. both methods i plan to pay bonus/comissions depending on how well the sales are.Īlso in terms of keeping track of hours worked. I'm inexperienced in this field as this is my first time doing this. now one concern is the method of payment. my business requires alot of cold calls so i want to outsource about 3-5 agents to work daily for me. I am trying to outsource a small call center for my startup business here in Toronto.
0 Comments
Leave a Reply. |