10
95%

Ran 29 Jan 2016 01:39AM UTC

Jobs 1

Files 0

Run time –

Badge

Embed ▾

pending completion

Build # 10

Build Type

Pull #2

travis-ci

Committed by

shaunbrady

Commit Message

Using custom fields to preserve ENUM types from postgres schema

I was not aware that the guacamole client (the war file) would use the
custom ENUM types at the top of the file (as opposed to just checking
for string equality).

To preserve these, I utilized custom fields based on this presentation
here:
https://wiki.postgresql.org/images/0/0b/Postgresql_django_extensions.pdf

Each of the models switched out CharFields for these EnumFields.

Because A) we could not automatically migrate the data and B) no one is
using (successfully) this project yet, we included two migrations, one
(0002) to remove the offending fields, and another (0003) to add in the
correct ones.

Because of the method by which we add the actual ENUM types themselves
in 0003, we needed to include sqlparse in the requirements.

Finally, our test was buffed up a little bit to prove we can still do
string comparison at the application level.

Pull Request Pull Request #2: Using custom fields to preserve ENUM types from postgres schema

Run Details

Jobs

ID	Job ID	Ran	Files	Coverage
1	10.1	29 Jan 2016 01:39AM UTC	0		Travis Job 10.1

Source Files on build 10

Detailed source file information is not available for this build.

nimbis / django-guac-auth / 10
95%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 10

nimbis / django-guac-auth / 10 95%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 10

nimbis / django-guac-auth / 10
95%

README BADGES
x