Subscribing to this thread as I'm also interested in peoples
solutions....

Not related to plugins, just a web app I'm doing at the moment I have
a (hacky) solution as follows:

Table A - id
Table B - table_a_id (set as not required)

Step 1: Write row to table a
Step 2: get the max(id) of table a - ie: the last row written
Step 3: write the value of step 2 to Table B in the table_a_id row

Pretty hacky as I said, and open to a race condition, but for what I'm
using it for that is pretty unlikely... Still not something I want to
keep there long term but it's working for now so I can move along to
other parts of the site I'm doing...

On Jan 25, 10:55 pm, lking <[email protected]> wrote:
> hi, James.
> i'm not sure if here is priorty, but i noticed that model don't want
> to
> builds if you use foreignClass option in the definition of foreign key
> for plugins.
> but if you use foreignTable option, model builds ok.
> no matter where defined foreign table in the model or in some plugin.
>
> hope it helps bit.
>
> On 24 янв, 09:58, James <[email protected]> wrote:
>
> > This is related to my other post about sfMultisiteThemePlugin and  
> > sfMultisiteGuardPlugin.  in the them plugin we have a profile table,  
> > is there a way to make the id of that table a foreign relation to a  
> > table in the sfMultisiteGuardPlugin.  I tried getting errors saying  
> > that it can't.  I am assuming because it's building the  
> > sfMultisiteGuardPlugin table before the table in sfMultisiteTheme  
> > plugin.  Is there a way for one plugin schema to take priority in the  
> > build process over the other?
>
> > Thanks,
> > James

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony developers" 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/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to