Creating two migrations at the same time

[0legovich]

When creating a migration file, goose adds a prefix in timestamp format with precision to the second. If you run the goose create command twice in a second, you will get unexpected behavior:

➜  goose create test
2024/02/29 16:39:34 Created new file: 20240229133934_test.go
➜  goose create test
2024/02/29 16:39:34 goose run: failed to create migration file: %!w(<nil>)

Error in the line https://github.com/pressly/goose/blob/master/create.go#L61

To be honest with the user, I think it is necessary to return an error indicating that such a file already exists.

[mfridman]

To be honest with the user, I think it is necessary to return an error indicating that such a file already exists.

Good catch, we should certainly expose a better error like "file already exists".

[TomerShor]

@mfridman is there any option for a version prefix other than timestamp?
The docs recommend using sequential versions but is it supported OOB or should we manually change them?

[mfridman]

Yep, goose supports both timestamp (effectively very large numbers) and sequential numbers.

goose create some_file sql -s                    
2024/12/31 08:17:19 Created new file: 00001_some_file.sql

The -s flag instructs goose to create "sequential"-ly numbered migrations. The leading 0's are there for alignment, can be 01, 001, 0001, the default is 5 digits.

[TomerShor]

@mfridman thanks!
Is the 5-digit padding also configurable?

[mfridman]

It's not configurable via the goose CLI (at least not today, something we might consider if there's enough demand).

There is the goose.CreateWithTemplate if you're using it as a library.

In another project I worked on we just create a 00N.sql files with bash. Lots of options.