One database sounds much easier.
It's probably easier to have users sign up first and then figure out what
type of user they are. Although it wouldn't be that hard to first determine
what type of user they are and then use a custom registration form
(http://web2py.com/books/default/chapter/29/7
Instead of a table within the main database of this webapp !! simply
because, a SRA or a league wants control and rights ...a league will want
more admin features over their own information .. more than clubs do ! ...
In short ... this is a webapp for Canada, somekind of a Full Soccer Sports
socia
Why do you say this: A league will most definitely needs its own database
instead of a table ?
I ask because it's probably not true.
On Wednesday, June 20, 2012 10:12:13 AM UTC-4, Don_X wrote:
>
> A league will most definitely needs its own database instead of a table
> ... while a team can hav
You'll almost certainly want separate tables each for teams, clubs and
leagues. Then you probably do one of these two choices:
db.define_table('team', Field('name'), Field('members', 'list:reference
auth_user'))
OR
db.define_table('team', Field('name'))
db.define_table('team_member', Field('au
A league will most definitely needs its own database instead of a table ...
while a team can have its own table within that league database !!! ... but
can a database be created on the fly within the app upon registration ??
On Wednesday, 20 June 2012 10:02:27 UTC-4, Don_X wrote:
>
> Hello,
>
>
5 matches
Mail list logo
