Stored procedures, while seemingly convenient, are actually not a good idea if you want to ensure your application remains properly database abstracted/agnostic. Stored procedures are in most cases not transferable between database type. For example, MySQL handles stored procedures very differently to MSSQL and there are differences as well to PostgreSQL.
In my development I avoid stored procedures and only use them as a last resort and even then as little as possible and reluctantly. Usually you can replicate what a stored procedure does in code and so they are not actually necessary. If you do use Propel custom queries you will probably need to look at using the doSelectRS (Propel 1.2) or doSelectStmt(Propel 1.3 and up) to accomplish it, but bear in mind the implications if you need to switch databases. On Mon, Sep 28, 2009 at 2:42 AM, dagger <strategy.vs.lo...@gmail.com> wrote: > > Hi, > > in my current project I have to connect to a remote system and execute > some stored procedures then get the returned data and save it on to > the local database... Is there a way I can achieve this through > symfony or would I have to bank on plain php? > > Your time n help is highly appreciated... Thx > > > -- Gareth McCumskey http://garethmccumskey.blogspot.com twitter: @garethmcc --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@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 -~----------~----~----~----~------~----~------~--~---
