UUID's

Hey Stéphane,

I just downloaded a fresh version of this course code and was able to execute migrations successfully in both start/ and finish/ folders. Did you download the course code and started from start/ directory? If so, it sounds like you have a bad migration, please, double-check the migration you created.

And good catch on "doctrine:schema:create" command - if it's a project for learning purposes and you don't care about real data in the DB - that's a totally valid way. For production, you may want to fix your migration otherwise you will lose real data.

Cheers!

Hey Zack F. !

> Why not use UUID and ULID from Symfony https://symfony.com/blog/ne... ?

Excellent question! Simply because this tutorial predated that feature... by about 2 months :). It was actually introduced already by the time we recorded this (so I knew about it), but it wasn't released stable yet. I mention this here - https://symfonycasts.com/sc... - but overall, it shouldn't make any difference, except that (maybe) using the Symfony UUID component will be even easier to integrate (though using ramsey is also pretty easy).

> And what is the difference between uuids and ulids and which one you encourage to go for

To be honest, I don't know much about these. But from some quick looking, it seems to me like, in practice, ULIDs are... a more awesome version of UUIDs. A ULID might be less random (as they have the created time encoded + are sortable)... but, unless the "created time" is sensitive to be shared publicly, that's kind of an awesome feature! And so is "sortability" - it's kind of nice to be able to sort database records by ULID and have them be in order. So honestly... yea... go for ULIDs! they're also prettier as URLs ;). I don't see any real disadvantage to them.

Cheers!

Hi, I´ve been trying to use the new Symfony UID, but having trouble on the Doctrine Type as the doctrine migration tries to create an BINARY(16) column instead of CHAR(36) as on the video. I´m using MySQL.

Is there a way to update symfony uuid type to use char(36) or it is better to just use the Ramsey as in the course.

Hey Erico Vasconcelos!

I don't know too much about this, but the Symfony version is definitely made to use a REAL UUID type (if your database supports it, which I believe MySQL does not) else it ALWAYS uses binary. Binary is more of a pain to deal with, but it's more efficient, which is why Symfony chose to only offer that. So if you want to use MySQL and want the string representation, then stick with ramsey :). But know that there could be some performance issues (these are often overblown, but it could be a real problem).

Cheers!

Hey Tuan Vu !

Very good question. And, I think this "advantage" is less common than I originally thought, but it does come in handy sometimes. Here's an example. Suppose you have a list of... products on a page. At the bottom of the list, you have an "add new product" button. When you click that, it instantly adds a new row to the table that renders the new product data (probably with blank or dummy values to start). It also "rolls out" a form on the sidebar with the product fields. As you type into those fields, the new row at the bottom of the table fills in with the new data automatically.

In this situation, if you're using something like React or Vue, you likely have some "products" state/data, which you're looping over to create the rows in the table. When you click "add new product", in order to add the new row immediately (even before saving), you'll add a new item to the "products" data. That will new item will need to have a unique key. You *could* create a fake key, then update it after you save (and get the new id), but it's not as smooth and it would actually cause Vue/React to re-render that row like new item.

So, in short, you need to have a situation where you're already rendering an item even *before* it's saved. It's not the normal situation, but hopefully that answers your question :).

Cheers!