Massimo will correct me if I'm wrong, but I think there is something
wrong with the general approach if one application needs to know/use
an another application's model. You're either try ing to split
something into two apps that is logically one, or you are trying to
make an app from something that is a module. Even with plugin style
apps (like t2) what's inside the plugin is a black box to the app. The
only exception to this might be some configuration related stuff, but
even there, I'd say it's better to use softlinks or similar than do
convoluted SQLDB-s like above.
For such cases, a web2py level solution could be perhaps that the
admin app acts as a registry for the other apps where they can store
custom settings and then invoke the adequate controllers to serve them
back the common data.
On Nov 9, 2:58 pm, Grahack <[EMAIL PROTECTED]> wrote:
> On 8 nov, 23:10, mdipierro <[EMAIL PROTECTED]> wrote:
>
> > if this is a SQLite db you can do
>
> > db=SQDB('sqlite://../../baseapp/models/storage.db')
>
> > db.define_table(.....,migrate=False) # you need to redefine the tables
>
> I think you meant sqlite://../../baseapp/DATABASES/storage.db.
> Mmf, it works great but, as we all know, redifining the tables is code
> duplication.
> I cannot believe you didn't found a trick yet.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
