Change the logmsg and description fields for events and alarms to text object.
Description
We have a client who makes heavy use of both the description and logmsg fields in events and alarms. There is no real reason why they can't be bigger than 4000 and 256 characters, respectively.
This enhancement is to make them "text" instead of "varchar" types. Should actually speed things up a little.
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Benjamin Reed February 2, 2011 at 5:17 PM
Also, this broke some unit tests. Removing the Constants.format() method meant we were sometimes pushing nulls to the database, which is not legal in PostgreSQL.
I've fixed this in 1.8 and master:
[1.8 477c693] fix for changes made for [master d19e4fd] fix for changes made for
Benjamin Reed February 2, 2011 at 1:56 PM
FYI, the push doesn't make it obvious what commits actually did the fixing. In this case, it's ac62f80446025d0e156fc196f59020ddf3647d32 in 1.8, and f60a782e0de2d42dc543339bf19a421ac4916ad6 in master.
We have a client who makes heavy use of both the description and logmsg fields in events and alarms. There is no real reason why they can't be bigger than 4000 and 256 characters, respectively.
This enhancement is to make them "text" instead of "varchar" types. Should actually speed things up a little.