Re: Re: [symfony-users] Extending a plugin schema (propel)

2009-12-11 Thread patrick
Hi there, 

unfortunately this email address no longer accepts mail.

For web enquiries please contact DDNS on 03 9815 6868 or i...@ddns.com.au

For support related issues please email supp...@ddns.com.au

Kind Regards,

Domain Admin


--

You received this message because you are subscribed to the Google Groups 
"symfony users" group.
To post to this group, send email to symfony-us...@googlegroups.com.
To unsubscribe from this group, send email to 
symfony-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/symfony-users?hl=en.




Re: [symfony-users] Extending a plugin schema (propel)

2009-12-11 Thread Bert-Jan
I've found the problem: my plugins are symlinked (since they're shared) 
which work fine for loading them but the path correction in 
sfPropelBaskTask.class.php#134 doesn't compensate for this. It uses 
absolute paths for the schemas which messes things up:

/usr/home/bertjan/cowboys-1.2/dcModelPlugin/config/schema.yml

is converted to a custom schema name

_usr_home_bertjan_cowboys-1.2_dcModelPlugin_schema.custom.yml

which should have been

dcModelPlugin_schema.custom.yml

I'm leaving on holiday in a few hours so I don't have time to create a 
patch for this.


Bert-Jan wrote:
> Hi Folks,
>
> I'm trying to extend the schema of my plugin as described in 
> http://www.symfony-project.org/book/1_2/17-Extending-Symfony#Customizing 
> a Plug-In for an Application. Running symfony 1.2.11-DEV from the 1.2 
> svn branch.
>
> My plugin is named dcModelPlugin which contains the entire model for a 
> number of projects I have running on the same codebase.
> For the project I'm working on right now I need to add some fields to a 
> few tables and some tables, but they need to stay in this project only.
> I've created /config/dcModulePlugin_schema.custom.yml, put only the 
> changes I need in there, made the package and phpName attributes 
> identical, and propel:build-model completely ignores it.
> When I try the same thing but call the project's schema schema.yml too, 
> then I get errors about foreign key references to non-existing tables. 
> Strange enough I've just removed the foreign table reference and only 
> left the field definition and the error disappeared, but nothing changes 
> in the model classes. Then I put the foreign table reference back in and 
> the error stays away, but still no changes in the model classes.
> I've tried changing the package of both the plugin and the project from 
> plugins.dcModelPlugin.lib.model to lib.model and vice versa, but nothing 
> changes. When I change the plugin's schema package to lib.model and 
> remove the project's own schema it *still* doesn't build the model 
> classes in
> lib.model.
>
> I've tried this extending of a plugin's schema several times before in 
> the past months and never got a single usable result from it.
> Can someone please confirm that it actually works with propel ?
> Has it ever worked ?
>
> Thanks,
> Bert-Jan
>
> --
>
> You received this message because you are subscribed to the Google Groups 
> "symfony users" group.
> To post to this group, send email to symfony-us...@googlegroups.com.
> To unsubscribe from this group, send email to 
> symfony-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/symfony-users?hl=en.
>
>
>   

--

You received this message because you are subscribed to the Google Groups 
"symfony users" group.
To post to this group, send email to symfony-us...@googlegroups.com.
To unsubscribe from this group, send email to 
symfony-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/symfony-users?hl=en.