[Rt-devel] RT 3.3 Custom Field question
Todd Chapman
rt at chaka.net
Fri Nov 19 10:33:26 EST 2004
Where in the RT interface this option is set/cleared?
On Fri, Nov 19, 2004 at 11:01:07AM -0500, Jesse Vincent wrote:
> "Show this custom field value when listing current values"
>
> We keep old values around because we show them in ticket history.
>
>
> On Fri, Nov 19, 2004 at 10:20:20AM -0500, Todd Chapman wrote:
> > What does the 'Disabled' field mean for ObjectCustomFieldValues?
> >
> > The comment below doesn't mean anything to me...
> >
> > CREATE TABLE ObjectCustomFieldValues (
> > id INTEGER NOT NULL AUTO_INCREMENT,
> > CustomField int NOT NULL ,
> > ObjectType varchar(255) NOT NULL, # Final target of the Object
> > ObjectId int NOT NULL , # New -- Replaces Ticket
> > SortOrder integer NOT NULL DEFAULT 0 , # New -- ordering for multiple
> > +values
> >
> > Content varchar(255) NULL ,
> > LargeContent LONGTEXT NULL, # New -- to hold 255+ strings
> > ContentType varchar(80) NULL, # New -- only text/* gets searched
> > ContentEncoding varchar(80) NULL , # New -- for binary Content
> >
> > Creator integer NOT NULL DEFAULT 0 ,
> > Created DATETIME NULL ,
> > LastUpdatedBy integer NOT NULL DEFAULT 0 ,
> > LastUpdated DATETIME NULL ,
> > Disabled int2 NOT NULL DEFAULT 0 , # New -- whether the value was
> > +current
> > PRIMARY KEY (id)
> > ) TYPE=InnoDB;
> >
> >
> > Also, does it indicate that there is an RT bug when both of
> > these records are in the table?:
> >
> > mysql> select * from ObjectCustomFieldValues where ObjectId=517 and Content='123';
> > +------+----------+-------------+---------+---------+---------------------+-----
> > +----------+---------------------+------------+--------------+-------------+----
> > +-------------+-----------+----------+
> > | id | ObjectId | CustomField | Content | Creator | Created |
> > +LastUpdatedBy | LastUpdated | ObjectType | LargeContent | ContentType |
> > +ContentEncoding | SortOrder | Disabled |
> > +------+----------+-------------+---------+---------+---------------------+-----
> > +----------+---------------------+------------+--------------+-------------+----
> > +-------------+-----------+----------+
> > | 6466 | 517 | 1 | 123 | 71 | 2004-11-16 19:12:16 | 71 | 2004-11-16 19:19:15 | RT::Ticket | NULL | NULL | | 0 | 1 |
> > | 6468 | 517 | 8 | 123 | 71 | 2004-11-16 19:52:34 | 71 | 2004-11-16 19:54:55 | RT::Ticket | NULL | NULL | | 0 | 1 |
> > | 6473 | 517 | 1 | 123 | 71 | 2004-11-16 20:32:14 | 71 | 2004-11-16 20:32:14 | RT::Ticket | NULL | NULL | | 0 | 0 |
> > +------+----------+-------------+---------+---------+---------------------+-----
> > +----------+---------------------+------------+--------------+-------------+----
> > +-------------+-----------+----------+
> > 3 rows in set (0.00 sec)
> >
> > _______________________________________________
> > Rt-devel mailing list
> > Rt-devel at lists.bestpractical.com
> > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel
> >
>
> --
More information about the Rt-devel
mailing list