Dar contraseñas a los usuarios

Hey @JDCrain ,

Ah, I see now :) Yeah, seems someone was testing that query on different DB structure and didn't tweak it to match the tutorial code, I fixed it :)

Thanks for the head ups!

Cheers!

Hey @JDCrain ,

What exactly confuses you in that? :) Could you share more info?

Cheers!

Hey Easwaran,

Hm, that should just work out of the box, not sure what exactly goes wrong in your case. First of all, please double-check the server version specified in your DB connection, either in the DATABASE_URL or in Doctrine config files, see "server_version" in https://symfony.com/doc/current/reference/configuration/doctrine.html . Also, double check your Doctrine config files that you don't have any custom options that may override that behavior.

But in your application, you can easily fix it with the validation constraints, then when you save the form without the required fields the validation will fail and the form will render an error for you avoiding saving the invalid data. That mostly solves your issue. About the "doctrine:query:SQL" - that's more complex, it just should work the same way your SQL console works, not sure. But that sounds like an edge case for admins anyway, it should not affect your users because users' input may be validated with validation constraints as I said above.

I hope that helps!

Cheers!

HI @Rufnex,

Eeasy-peasy, you can configure everything in security.yaml here the docs https://symfony.com/doc/current/reference/configuration/security.html#reference-security-firewall-form-login

Cheers!

Hi sadikoff,

thank you .. thats clear. What I meant I, in the database table the password field is called usr_password and not password. Is it possible to configure that too?

Thank you again.

Of course, you have total control over your Entity. You can use name property on #[ORM\Column()] attribute, and many overs BTW :-)

Cheers

OMG . thats fu*** easy! Thank you ;o)

Hey triemli,

And probably not, did you get any issues with that? If yes, can you please share you DB version so we can find why that's not work for you?
If you create a not null field without default data mysql should just add this field with empty data, but probably that is something depending on configuration or server version.

Cheers

Maybe because I used Postgres.
First migration:
` $this->addSql('CREATE SEQUENCE users_id_seq INCREMENT BY 1 MINVALUE 1 START 1');

    $this->addSql('CREATE TABLE users (id INT NOT NULL, email VARCHAR(180) NOT NULL, roles JSON NOT NULL, first_name VARCHAR(255) DEFAULT NULL, PRIMARY KEY(id))');
    $this->addSql('CREATE UNIQUE INDEX UNIQ_1483A5E9E7927C74 ON users (email)');`

Second
$this->addSql("ALTER TABLE users ADD password VARCHAR(255) NOT NULL DEFAULT ''");

Yeah that's the key, we are using mysql for tutorial, sounds like we should write a note about it, thanks for tip!

Cheers!

On Postgres I had to add some extra escaped quotes round user to get the migration to complete:
$this->addSql("ALTER TABLE \"user\" ADD password VARCHAR(255) NOT NULL DEFAULT''");

Hey gazzatav

I bet that is because you are using "user" as table name, and this word is reserved. but tutorial uses "users" and that can be ok

Cheers

Hi @Vladimir, you are right that 'user' is a reserved word in postgresql and several other sql standards but I have used the class User exactly like the tutorials (there is no use of 'users' in the class). Doctrine is choosing table names not me! It may be that Doctrine chose 'users' for your dbms and version. Maybe Doctrine's knowledge of the dbms is so good it knows how closely it can keep to entity names. Out of interest, the postgresql documentation does say that it's possible to use a reserved word as a bare table name without creating an 'as' alias but anyway Doctrine always seems to create aliases. If I use psql to check my database, when I use the '\d user' command to describe the table, it describes the one Doctrine made. However, if I run 'select * from user;' the result comes from the admin table which postgres made! If I change the query to use 'public.user' I get the results from the fixtures.

Whoops, I missed somehow that tutorial uses 'user'. You can always force doctrine to use any table name you need with @ORM\Table() annotation =)

Cheers