TEXT type in MySQL

General Discussion
1

Go ahead and log it as one. It comes from the “try to convert from what you are saying to something more cross-database consistent” logic which is a bit of a mess in 2.0 and is the main focus of 3.0. I’ll make sure it stays consistant in 3.0.


Nathan

2

I cannot use the TEXT type to the changelog.xml. Everytime i use it, liquibase automaitically change the type into LONGTEXT and create the table. Has anyone suffered this issue ?
[Update] it works fine if i set it as ‘longtext’, ‘mediumtext’ or ‘tinytext’. Only the ‘text’ type will be converted into ‘longtext’. Is this considered as a bug?

3

The bug was created? Is there a workaround?

4

 that can be used as workaround.

5

Any quick solution for the false conversion in MYSQL? ie TEXT => LONGTEXT. Using the extension seems reasonable. Can anyone post the steps required to add it? 



6

I am having this problem in a fairly recent liquibase version. Was it ever fixed?

7

It hasn’t been yet. I created https://liquibase.jira.com/browse/CORE-1560 to track the fix and will fix it in 3.1.0


Nathan

8

Thanks Nathan. This is a pressing issue, any chance you have a patch I can apply right now, or a describe a workaround for us?


We use both longtext and text, so we cannot simply replace.


Thanks.

9

No patch yet, but it is something I’m planning to work on in the next couple weeks. Sorry.


Nathan

10

Same problem with TIMESTAMP, liquibase always converts TIMESTAMP to TIMESTAMP WITH TIME ZONE . Here is how I fixed it. I added a tag to your change set, like below.
      
            
         
Very useful to have this to tweak the ouput SQL generated by LB.

Zoom

11

So, something like for that particular changeset should fix your problem.
Zoom