{"push_id":1075779410,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"8f4b00462a12f395bad4d9a98000596e6d007b54","before":"98cdb33ff37b517fe9b23c0c3b3fc076b2e4db42","commits":[{"sha":"8f4b00462a12f395bad4d9a98000596e6d007b54","author":{"email":"d7e19930cc1f42c2d0781f4d9e6f1fe5891bf9cf@seantheprogrammer.com","name":"Sean Griffin"},"message":"Change `VarChar` to be an alias to `Text` (#288)\n\nThis removes the `VarChar` type entirely, unifying it with text.\r\nThis simplifies the interaction with things like SQL functions, and\r\nremoves gotchas like `lower` not working with text columns. SQLite will\r\nbe unaffected by this change. PG is mostly unaffected. However, it\r\ndoesn't treat `varchar[]` arrays as equivalent to `text[]`. INSERT and\r\nUPDATE will continue to work, but other operators/functions will error\r\nout. Since they have identical representations in the database, I'm fine\r\nwith introducing the weird ideosynchracy of \"use `text[]` instead of\r\n`varchar[]`, as we remove some much larger warts.\r\n\r\nThere is some more in depth research/reasoning at #287.\r\n\r\nOne other visible effect here is that `VarChar` can no longer be\r\nreferenced in expression positions, as it is not a struct. This can be\r\nseen in the change made to `diesel_tests::schema_dsl`. Since the structs\r\nhave no size and no method, there's never any reason to use them in\r\nexpression positions, and I've simply replaced that field entirely.\r\n\r\nClose #287","distinct":true,"url":"https://api.github.com/repos/diesel-rs/diesel/commits/8f4b00462a12f395bad4d9a98000596e6d007b54"}]}