[mythtv-commits] Ticket #6811: Invalid default value for BLOB field in MySQL CREATE statement for mythweb_sessions table

[MythTV]

#6811: Invalid default value for BLOB field in MySQL CREATE statement for
mythweb_sessions table
----------------------------------------------------+-----------------------
 Reporter:  Jonathan Martens <jonathan at snetram.nl>  |        Owner:  xris
     Type:  defect                                  |       Status:  new 
 Priority:  major                                   |    Milestone:  0.22
Component:  Plugin - MythWeb                        |      Version:  head
 Severity:  medium                                  |   Resolution:      
  Mlocked:  0                                       |  
----------------------------------------------------+-----------------------

Comment(by anonymous):

 Replying to [comment:1 anonymous]:
 > Are you planning also to audit main MythTV DB?  If you want to see real
 fireworks, turn on MySQL mode (STRICT_TRANS_TABLES or STRICT_ALL_TABLES)
 and see what happens.  There are many cases of "NOT NULL" in the myth
 schema that are not respected in code (frequently dates and text fields),
 but by default MySQL allows it anyway.  mythfilldatabase, manual
 recordings, and channel scanner are just a few things that break if you
 activate strict mode.

 No, not for the moment. The fact whether a column is specified a default
 value of NOT NULL is not really an issue here.
 I only reported show stoppers I found in trying to compile and run MythTV
 on Windows. Specifying default values for column types (TEXT, BLOB) that
 do _not_ support default values which makes queries fail and hence
 database updates fail.
 Specifying whether or not columns are allowed to hold a NULL value by
 default will not break upgrades AFAICT.

 In this case MythWeb won't show the interface as the creation of the
 mythweb_sessions table is not created.

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/6811#comment:2>
MythTV <http://www.mythtv.org/>
MythTV