(Draft) Trying to fix BIGINT issues

[0xFEEDC0DE64]

I think we should not only cover BIGINT and not only in CREATE TABLE statements...

but this is for now what fixes my problem with wp-statistics

[mattbucci]

Most of these regexes are already case insensitive.

I think we can just add an "i" to the end of

postgresql-for-wordpress/pg4wp/rewriters/CreateTableSQLRewriter.php

Line 99 in 716db95

$pattern = "/(" . $numeric_types_imploded . ")\(\d+\)/";

This should make this case insensitive and either bigint variation should match

[mattbucci]

Make regexes match insensitively

[mattbucci]

Looks like we have a failing test, but it's the test itself that is incorrect.

1) rewriteTest::test_it_removes_character_sets
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
platform varchar(255),
version varchar(255),
location varchar(10),
- user_id BIGINT(48) NOT NULL,
- page_id BIGINT(48) NOT NULL,
+ user_id BIGINT NOT NULL,
+ page_id BIGINT NOT NULL,

[0xFEEDC0DE64]

Have you found another solution for this problem?

[mattbucci]

See #131