Hi Dustin thank you very much for the information, it works perfectly! Carlos
On 26 mar, 22:22, Dustin Whittle <[EMAIL PROTECTED]> wrote: > Carlos, > > Please use the configure:database task or edit the propel.ini with the new > connection information. Also, see the propel 1.3 upgrade > guide:http://propel.phpdb.org/trac/wiki/Users/Documentation/1.3/Upgrading. > > You should also copy the new propel.ini from my branch: > > http://trac.symfony-project.com/browser/branches/dwhittle/1.1/lib/tas... > ator/skeleton/project/config/propel.ini > > - Dustin > > On 3/26/08 12:53 PM, "Carlos Cuenca" <[EMAIL PROTECTED]> wrote: > > > > > Also, > > > after creating a username carlos for the database (which is my login name on > > the computer), executing the command connects correctly, but it does not > > take > > into account the database name: > > > [propel-sql-exec] Executing statements in file: > > /home/carlos/workspace-php/Mu/data/sql/lib.model.schema.sql > > [propel-sql-exec] Our new url -> mysql://ma:[EMAIL PROTECTED]/Mu > > [propel-sql-exec] Executing file: > > /home/carlos/workspace-php/Mu/data/sql/lib.model.schema.sql > > [propel-sql-exec] Failed to execute: > > > DROP TABLE IF EXISTS `aseguradora` > > [propel-sql-exec] SQLSTATE[3D000]: Invalid catalog name: 1046 No database > > selected > > [propel-sql-exec] Failed to execute: > > > CREATE TABLE `aseguradora` > > ( > > `id` INTEGER NOT NULL AUTO_INCREMENT, > > `nombre` VARCHAR(255), > > PRIMARY KEY (`id`) > > )Type=InnoDB > > [propel-sql-exec] SQLSTATE[3D000]: Invalid catalog name: 1046 No database > > selected > > [propel-sql-exec] 2 of 4 SQL statements executed successfully > > > Carlos > > > On Wed, Mar 26, 2008 at 8:44 PM, Carlos Cuenca <[EMAIL PROTECTED]> > > wrote: > > >> Hi, > > >> I had setup symfony as we talked about. I am testing with a small > >> schema and I get the following error while running propel:insert-sql. > >> I think it is not using the dsn defined: > > >> propel > insert-sql: > > >> [propel-sql-exec] Executing statements in file: /home/carlos/workspace- > >> php/Mu/data/sql/lib.model.schema.sql > >> [propel-sql-exec] Our new url -> mysql://ma:[EMAIL PROTECTED]/Mu > >> Execution of target "insert-sql" failed for the following reason: /var/ > >> Symfony-Hwsol/lib/plugins/sfPropelPlugin/lib/vendor/propel-generator/ > >> build-propel.xml:275:1: [wrapped: SQLSTATE[28000] [1045] Access > >> denied for user 'carlos'@'localhost' (using password: NO)] > >> [phing] /var/Symfony-Hwsol/lib/plugins/sfPropelPlugin/lib/vendor/ > >> propel-generator/build-propel.xml:275:1: [wrapped: SQLSTATE[28000] > >> [1045] Access denied for user 'carlos'@'localhost' (using password: > >> NO)] > > >> as you can see it is not using the data defined on databases.yml: > >> all: > >> propel: > >> class: sfPropelDatabase > >> param: > >> dsn: mysql://ma:[EMAIL PROTECTED]/Mu > > >> I don't know if its related with your branch or with the 1.1 distro. > >> Any hints? > > >> Carlos > > >> On 26 mar, 01:52, Carlos Cuenca <[EMAIL PROTECTED]> wrote: > >>> > Ok, with today's announcement I will give a try to 1.1 with your > >>> > propel 1.3 plugin, I will keep you informed. > > >>> > Thanks > >>> > Carlos > > >>> > On 24 mar, 05:44, Dustin Whittle <[EMAIL PROTECTED]> > >>> > wrote: > > >>>> > > Carlos, > > >>>>> > > > Thank you very much for your fast answer. > > >>>>> > > > So basically I could download 1.1 stable from the repo and replace > the > >>>>> > > > 1.1/lib/plugins/sfPropelPlugin with the one in your branch. Is it > >>>>> > > > enough? > > >>>> > > Yes, except in sfPropelLogger, you need to change ::ERROR to ::ERR (I > use > >>>> > > more verbose error constants, not the pear/propel constants). > >>>> Otherwise, > >>>> > > everything else should work (though I have not tested extensively). > > >>>> > > Please let me know if you find any issues along the way. > > >>>> > > Cheers, > > >>>> > > Dustin > > >>>>> > > > Carlos > > >>>>> > > > On 22 mar, 23:56, Dustin Whittle > >>>>> <[EMAIL PROTECTED]> > >>>>> > > > wrote: > >>>>>> > > >> Carlos, > > >>>>>> > > >> Do not use my branch for a production project. The code is > >>>>>> > > >> stable > >>>>>> and there > >>>>>> > > >> are 8000+ passing tests, but there are undoucumented/unsupported > >>>>>> nuances in > >>>>>> > > >> my branch. You should use symfony 1.1 stable and the propel 1.3 > >>>>>> plugin. When > >>>>>> > > >> 1.1 is labeled stable, I will export propel 1.3 from my branch > >>>>>> > > >> as > >>>>>> a plugin. > > >>>>>> > > >> All of the useful tweaks that are in my branch, will get merged > >>>>>> > > >> in > >>>>>> to 1.1. > >>>>>> > > >> If there is any functionality specifically you want merged, > >>>>>> > > >> please > let me > >>>>>> > > >> know and we can discuss merging it into 1.1 stable. > > >>>>>> > > >> Cheers, > > >>>>>> > > >> Dustin > > >>>>>> > > >> On 3/22/08 9:07 AM, "Carlos Cuenca" <[EMAIL PROTECTED]> > wrote: > > >>>>>>> > > >>> 1) Do you have an estimation for the final release of sf1.1? > >>>>>>> > > >>> 2) As I will process quite amount of data, I was thinking on > using > >>>>>>> > > >>> propel 1.3 I had been following dwhittle branch and commits > >>>>>>> > > >>> and > the > >>>>>>> > > >>> excelent work he is doing here. My question for this is how > >>>>>>> usable is > >>>>>>> > > >>> that branch, and if it could be ready for use on production. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
