Consider colons as a token separator

[pmalouin]

I bumped into tokenization problems on PostgreSQL with statements of the form:
CREATE TABLE base_table (
base_table_id integer DEFAULT nextval('base_table_seq'::regclass) NOT NULL
);
The parser considers "'base_table_seq'::regclass" to be a full token, but it should be considered as 2 tokens:
"'base_catalog_table_seq'" and "regclass"

Now I haven't tested this with other rdbms and I'm not sure this should be applied to all of them.

[axelfontaine]

Hi Patrick,

thanks for contributing this! One small thing: could you also include a test case in future pull requests? It makes it so much easier to validate things.

I've added you to the hall of fame: http://flywaydb.org/contribute/hallOfFame.html

Cheers
Axel

[pmalouin]

Hi Axel,
Thanks! I will add tests next time!
Patrick

[pmalouin]

Hi Axel,
We're planning on migrating a big PostgreSQL project to Flyway, and this fix is necessary for us (100s of scripts with that syntax). I'd prefer not building from source and have an official release before we begin our work.
When do you expect to have a new official build for Flyway?
Thanks!

[axelfontaine]

Hi Patrick,

I am aiming for a 2.2 release by the end of next week, give or take a few days.

Cheers
Axel

[pmalouin]

That's great!
Patrick