1 Mar 2011 12:59
Re: [Trac-dev] Integer type for custom fields
Nick Piper <nick.piper <at> logica.com>
2011-03-01 11:59:07 GMT
2011-03-01 11:59:07 GMT
On 28/01/11 10:01, Steffen Hoffmann wrote: > Nick Piper wrote: >> I believe (also from the list at >> http://trac.edgewall.org/wiki/TracTicketsCustomFields) that most of the >> 'types' of custom fields are about the graphical representation of the >> field in the ticket page. > >> Is anyone aware of work to introduce some "data" types, such as >> integer/float/(date - but I know about >> http://trac-hacks.org/wiki/DateFieldPlugin). > > When I started to actually code something to solve Trac #1942 it has > been mentioned, that this _might_ be the last improvement upon the > mature but aged custom field implementation. Work should in general go > towards a major rework i.e. with new concept for the db backend storage > organization, that has been announced with buzz words like GenericTrac. I agree my patch for numeric fields is kind of temporary until a more generic field system is introduced. Hopefully one with less iterating over the fields list so much(Continue reading)>> One reason we'd really like the numeric types is so that we could add >> some 'aggregation' options to the query pages. For example, if there was >> a custom field 'cost', it would be great to be able to sum() those costs >> on the query page to provide a total. Doing that requires to know the >> field is a numeric type, as well as some niceties such as validation of >> user input, a nicer HTML widget for the user input, and so on. The >> actual storage to the database backend is likely to stay as strings
>> One reason we'd really like the numeric types is so that we could add
>> some 'aggregation' options to the query pages. For example, if there was
>> a custom field 'cost', it would be great to be able to sum() those costs
>> on the query page to provide a total. Doing that requires to know the
>> field is a numeric type, as well as some niceties such as validation of
>> user input, a nicer HTML widget for the user input, and so on. The
>> actual storage to the database backend is likely to stay as strings
>> 2. running trac-admin /var/tracprojects/OpenERP repository resync
>> "openobject-addons"
>> i get the error:
>> TimeoutError: Unable to get database connection within 0 seconds.
>> (TracError(u'Database "/var/tracprojects/OpenERP/db/trac.db" not found.',))
>> looks like trac-admin is looking for SQLite db...
> This is usually a permission issue, more precisely the user running
> trac-admin doesn't have permission to read trac.ini. I think we already
> have an open ticket for this issue.
>
oh, should I just use sudo trac-admin for the time being? or will I get
in other troubles?
RSS Feed