6.0.0-beta1
7/6/25

[#9052] Differences in the definition of several fields in the creation scripts for MSSQL
Summary Differences in the definition of several fields in the creation scripts for MSSQL
Queue Horde Base
Queue Version 3.3.8
Type Bug
State No Feedback
Priority 1. Low
Owners
Requester gloria.presedo (at) usc (dot) es
Created 05/21/2010 (5525 days ago)
Due 05/21/2011 (5160 days ago)
Updated 06/15/2010 (5500 days ago)
Assigned 06/01/2010 (5514 days ago)
Resolved 06/15/2010 (5500 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
06/15/2010 03:23:43 PM Jan Schneider State ⇒ No Feedback
 
06/01/2010 01:13:44 PM Jan Schneider Comment #2
State ⇒ Feedback
Reply to this comment
I don't see what the problem is. horde_prefs.sql is a generic SQL 
script, create.mssql.sql is specifically for MS-SQL.
05/21/2010 12:49:26 PM gloria (dot) presedo (at) usc (dot) es Comment #1
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Base
Due ⇒ 05/21/2011
Summary ⇒ Differences in the definition of several fields in the creation scripts for MSSQL
Type ⇒ Bug
State ⇒ Unconfirmed
Reply to this comment
There are differences in the definition of several fields in the 
creation scripts for MSSQL.

Pref_value field in the table horde_prefs is a type TEXT, according to 
the script create.mssql.sql, but according horde_prefs.sql is a 
VARCHAR(MAX).

The same is true
* datatree_data in horde_datatree
* vfs_data in horde_vfs
* history_desc in horde_histories
* history_extra in horde_histories
* alarm_params in horde_alarms
* alarm_text in horde_alarms
* alarm_internal in horde_alarms

Saved Queries