Error: sql/schema: unsupported dialect "libsql"

[arjunyel]

Error: sql/schema: unsupported dialect "libsql"

[arjunyel]

@haaawk is it possible to add Ent support to the TODO list? 😄 Thank you friend

[masseelch]

Can you provide me the output of atlas version, please?

[arjunyel]

@masseelch Thank you for taking a look friend! atlas version v0.15.1-143f43e-canary

[masseelch]

For versioned migrations, Atlas stores some meta-data about the migration process in a separate table / schema. We use Ent for this, but Ent does not have support for libsql which is the reason it does not work. (If I recall correctly, there was some issue with time.Time parsing).

cc @haaawk, who added the turso integration.

[haaawk]

We fixed the time.Time parsing in libsql client so maybe it will be enough to update it's version it Atlas. I will send a PR

[haaawk]

This might help #2341

[arjunyel]

Does libsql support still need to be added to ent for this to work?

[haaawk]

Does libsql support still need to be added to ent for this to work?

Not sure. It's been a while since I checked ent.

[arjunyel]

For versioned migrations, Atlas stores some meta-data about the migration process in a separate table / schema. We use Ent for this, but Ent does not have support for libsql which is the reason it does not work. (If I recall correctly, there was some issue with time.Time parsing).

cc @haaawk, who added the turso integration.

I think based on this message Ent is where the error is originating from

[asterikx]

I get the same error with Turso with versioned migrations, declarative workflow works just fine.

atlas version v0.15.1-96e920d-canary

[arjunyel]

@haaawk sorry for the ping again, is there somewhere we can officially request this feature and get it tracked?

[haaawk]

I put Ent support on my list but unfortunately there are many other items with higher priority at the moment.

libsql-client-go supports already time.Time so maybe it's enough to update the libsql-client-go version that atlas is using. I encourage you to give it a try :).

[arjunyel]

@PietervdWerk hi friend, how come you said this isn't an Ent issue when the Atlas maintainer above said they use Ent for the versioned migrations? Atlas does work already for declarative migrations