Thanks for the reply Luciano! I made a small modification in
symfony/vendor/Propel.php on line 487:

       try {
+++    $dsn['password'] = urldecode( $dsn['password'] );
           $con = Creole::getConnection($dsn);
      } catch (SQLException $e) {
           throw new PropelException($e);
      }

It worked... although I don't think it's a good practice modifying the
propel core! =)


On 6/1/07, Luciano A. Andrade <[EMAIL PROTECTED]> wrote:
>
> 1.- Do change your password.
> If yoy cant. 2.- You could use php insede a yaml file. (i think with
> <?=MYPASSWRD ?>)
>
> if you get the error at runing symfony propel-* you shuld try to copy
> you database to other mysql if you tring to build the schema.xml from
> the db, and insert the sql schema your self if you using
> "propel-insert-sql" (o create the db if "propel-build-db is the
> problem)
> PD: Note that symfony propel-build-all runs propel-build-model/sql
> propel-create-db (o propel-build-db can't remember) and
> propel-insert-sql in that order.
>
> On 5/31/07, Ville <[EMAIL PROTECTED]> wrote:
> >
> > Hi everybody!
> >
> > I'm trying to build an app based on an existing database wich has a
> > big password including '#', '$' and other ugly characters.
> > For the first error message, I had to get an urlencoded() password
> > (escaping didn't work), fine but the next error message killed me:
> >
> > [wrapped: connect failed [Native Error: Access denied for user
> > 'regtrb'@'10.7.2.254' (using password: YES)] [User Info: Array]]
> >
> > I tested on mysql console (locally connecting to the external server)
> > and the username/password is working.
> >
> > Any advice? Thanks!
> >
> > >
> >
>
> >
>

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

Reply via email to