Tickets :: [#6940] share_owner field length

Summary	share_owner field length
Queue	Kronolith
Queue Version	2.2
Type	Enhancement
State	Resolved
Priority	1. Low
Owners	Michael Rubinsky <mrubinsk (at) horde (dot) org>
Requester	tyuhas (at) email (dot) arizona (dot) edu
Created	06/16/2008 (159 days ago)
Due
Updated	06/17/2008 (158 days ago)
Assigned
Resolved	06/17/2008 (158 days ago)
Attachments
Milestone
Patch	No

06/17/2008	Michael Rubinsky	Comment #6	Reply to this comment
I noticed that in the *_shares_users table, the field user_uid has the same length issue. fixed. Along with all the other share applications.

06/17/2008	tyuhas (at) email (dot) arizona (dot) edu	Comment #5	Reply to this comment
fixed, and merging shortly. I noticed that in the *_shares_users table, the field user_uid has the same length issue. Sorry I didn't catch that earlier.

06/17/2008	Michael Rubinsky	Comment #4 State ⇒ Resolved	Reply to this comment
fixed, and merging shortly.

06/17/2008	CVS Commit	Comment #3	Reply to this comment
Changes have been made in CVS for this ticket: http://cvs.horde.org/diff.php/ansel/scripts/sql/ansel.sql?r1=1.21&r2=1.22&ty=u http://cvs.horde.org/diff.php/genie/scripts/sql/genie.mssql.sql?r1=1.6&r2=1.7&ty=u http://cvs.horde.org/diff.php/genie/scripts/sql/genie.sql?r1=1.7&r2=1.8&ty=u http://cvs.horde.org/diff.php/genie/scripts/upgrades/2008-04-18_add_sql_share_tables.sql?r1=1.2&r2=1.3&ty=u http://cvs.horde.org/diff.php/ingo/scripts/sql/ingo.oci8.sql?r1=1.6&r2=1.7&ty=u http://cvs.horde.org/diff.php/ingo/scripts/sql/ingo.sql?r1=1.9&r2=1.10&ty=u http://cvs.horde.org/diff.php/kronolith/scripts/sql/kronolith.mssql.sql?r1=1.9&r2=1.10&ty=u http://cvs.horde.org/diff.php/kronolith/scripts/sql/kronolith.mysql.sql?r1=1.13&r2=1.14&ty=u http://cvs.horde.org/diff.php/kronolith/scripts/sql/kronolith.oci8.sql?r1=1.13&r2=1.14&ty=u http://cvs.horde.org/diff.php/kronolith/scripts/sql/kronolith.pgsql.sql?r1=1.11&r2=1.12&ty=u http://cvs.horde.org/diff.php/kronolith/scripts/sql/kronolith.sql?r1=1.11&r2=1.12&ty=u http://cvs.horde.org/diff.php/kronolith/scripts/sql/kronolith.xml?r1=1.6&r2=1.7&ty=u http://cvs.horde.org/diff.php/kronolith/scripts/upgrades/2.1_to_2.2.pgsql.sql?r1=1.5&r2=1.6&ty=u http://cvs.horde.org/diff.php/kronolith/scripts/upgrades/2.1_to_2.2.sql?r1=1.5&r2=1.6&ty=u http://cvs.horde.org/diff.php/mnemo/scripts/sql/mnemo.mssql.sql?r1=1.5&r2=1.6&ty=u http://cvs.horde.org/diff.php/mnemo/scripts/sql/mnemo.oci8.sql?r1=1.4&r2=1.5&ty=u http://cvs.horde.org/diff.php/mnemo/scripts/sql/mnemo.sql?r1=1.9&r2=1.10&ty=u http://cvs.horde.org/diff.php/mnemo/scripts/sql/mnemo.xml?r1=1.3&r2=1.4&ty=u http://cvs.horde.org/diff.php/mnemo/scripts/upgrades/2.1_to_2.2.sql?r1=1.2&r2=1.3&ty=u http://cvs.horde.org/diff.php/nag/scripts/sql/nag.mssql.sql?r1=1.11&r2=1.12&ty=u http://cvs.horde.org/diff.php/nag/scripts/sql/nag.oci8.sql?r1=1.11&r2=1.12&ty=u http://cvs.horde.org/diff.php/nag/scripts/sql/nag.sql?r1=1.15&r2=1.16&ty=u http://cvs.horde.org/diff.php/nag/scripts/sql/nag.xml?r1=1.7&r2=1.8&ty=u http://cvs.horde.org/diff.php/nag/scripts/upgrades/2.1_to_2.2.sql?r1=1.3&r2=1.4&ty=u http://cvs.horde.org/diff.php/turba/scripts/sql/turba.mssql.sql?r1=1.4&r2=1.5&ty=u http://cvs.horde.org/diff.php/turba/scripts/sql/turba.oci8.sql?r1=1.4&r2=1.5&ty=u http://cvs.horde.org/diff.php/turba/scripts/sql/turba.pgsql.sql?r1=1.5&r2=1.6&ty=u http://cvs.horde.org/diff.php/turba/scripts/sql/turba.sql?r1=1.4&r2=1.5&ty=u http://cvs.horde.org/diff.php/turba/scripts/sql/turba.xml?r1=1.4&r2=1.5&ty=u http://cvs.horde.org/diff.php/whups/scripts/sql/whups.mssql.sql?r1=1.20&r2=1.21&ty=u http://cvs.horde.org/diff.php/whups/scripts/sql/whups.oci8.sql?r1=1.20&r2=1.21&ty=u http://cvs.horde.org/diff.php/whups/scripts/sql/whups.sql?r1=1.25&r2=1.26&ty=u http://cvs.horde.org/diff.php/whups/scripts/upgrades/2008-04-29_add_sql_share_tables.sql?r1=1.1&r2=1.2&ty=u

06/16/2008	Michael Rubinsky	Comment #2 State ⇒ Accepted Assigned to Michael Rubinsky	Reply to this comment
yea, not sure why that was only 32, especially since varchar only takes up the space used, up to the value specified (well, plus the extra byte or two for the size value but I digress...) Anyway, yea, this should also be made a VARCHAR(255)...and probably also needs to be done in the other share apps as well

06/16/2008	tyuhas (at) email (dot) arizona (dot) edu	Comment #1 Patch ⇒ Milestone ⇒ Queue ⇒ Kronolith Summary ⇒ share_owner field length Type ⇒ Enhancement Priority ⇒ 1. Low State ⇒ New	Reply to this comment
As installed, the share_owner field is a varchar (32). When you are using realms the share_owner field can get a bit large. I was tracking down why some people would not have a default calendar or be able to create and modify one. Turns out those with issues had their share_owner values truncated. Can the share_owner field be made bigger w/o causing issues?