They are treated as strings everywhere. Converting them to int causes problems
when using postgresql as the database backend because it doesn't automatically
cast them back to integer.
Change-Id: I9f0a5149d24a4c003409728e50376569c97e7325
Closes-bug: 1330490
(cherry picked from commit 3be62f878e8165cf3bce357a00b8a583773f7d3b)
Reviewed: https:/ /review. openstack. org/102754 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=a17a5005759 4027739c819264c ebb3405ee8be42
Committed: https:/
Submitter: Jenkins
Branch: stable/icehouse
commit a17a50057594027 739c819264cebb3 405ee8be42
Author: Ralf Haferkamp <email address hidden>
Date: Wed Jun 18 17:01:26 2014 +0200
Don't convert numeric protocol values to int
They are treated as strings everywhere. Converting them to int causes problems
when using postgresql as the database backend because it doesn't automatically
cast them back to integer.
Change-Id: I9f0a5149d24a4c 003409728e50376 569c97e7325 f3bce357a00b8a5 83773f7d3b)
Closes-bug: 1330490
(cherry picked from commit 3be62f878e8165c