That's a good question, Horus. :-/
I haven't tried that. Theoretically, db_cas.base_tags field could be
referenced because it needs the db object.
Let us know about your progress on it.
--
Vinicius Assef
On 07/06/2012 03:40 PM, Horus wrote:
Right viniciusban i agree. i don't want to perfo
*I will put all my tables in one app and call it a day!*
On Friday, July 6, 2012 2:40:32 PM UTC-4, Horus wrote:
>
> Right viniciusban i agree. i don't want to perform joins across
> databases explicitly i have never seen that in SQL
> BUT I can use the user id from the CAS provider to refer to
Right viniciusban i agree. i don't want to perform joins across databases
explicitly i have never seen that in SQL
BUT I can use the user id from the CAS provider to refer to other tables in
a database
let's say the *CAS* provider has this table called *auth_user* with a field
called *id*.
le
Short answer: manually.
You cannot connect (join or make a relation) fields among different
databases.
On 07/06/2012 02:16 PM, Horus wrote:
Yes I understand CAS is for central auth, so i have let the cas provider
be the app that takes care of login, registration, signup, what have
you; as i
Yes I understand CAS is for central auth, so i have let the cas provider be
the app that takes care of login, registration, signup, what have you; as
it should
the tables are being created, so I am assuming that the other apps should
be able to access the tables if they exist all in the same dat
Well CAS is for central authentication, not for sharing database tables ... .
The error you got simply says that your second app cant see tables from cas
provider app.
Additionally...
I currently have three apps, including CAS server
the case server app also contain other tables
db.define_table('base_tags',
Field('name', 'string', label='Tag', length=64,
required=True, notnull=True),
format='%(name)s'
)
and many
7 matches
Mail list logo
