Completely off the cuff and unverified: maybe you can use your
database syntax for cross db table referencing in the __storm_table__
attribute?
Something like:
class CRMThingie:
__grok_table__ = "CRMdb.sometable"
[...]
class LicIssuingThingie:
__grok_table__ = "lic_issuing_db.othertable"
[...]
Cheers, Leo
On Thu, May 15, 2008 at 10:46 PM, Glen Richards <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a use-case where I need to query across 2 separate databases.
>
> Database 1 is the backend of a CRM web-app that we use, but do not
> develop. Database 2 is the backend of a lic-issuing-app that we
> maintain ourselves.
>
> The same db server hosts both databases.
>
> Database 2 tables have foreign keys to database 1. Eg, an order in the
> lic-issuing-db has an associated account in the crm-db.
>
> Hard-coding the SQL, I have no problems querying across the 2 databases.
>
> I note on the Storm front page:
>
> "Storm works very well connecting to several databases and using the
> same Python types (or different ones) with all of them."
>
> I assumed that this meant my use-case above would be supported. Or is
> it referring to replicated databases?
>
> Am I dreaming thinking an ORM, specifically Storm, would be able to
> handle my use-case?
>
> If my use-case is do-able, can I get some tips? Ie, How can I tell a
> Store about my other database.
>
> Kind regards,
>
>
> Glen Richards
>
> --
> storm mailing list
> [email protected]
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/storm
>
--
storm mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/storm
