Re: charset; logical OR on filtering; list of dates

Nagy Gabor <[email protected]>
Newsgroups gmane.comp.bug-tracking.roundup.user
Message-ID <20210517012213.10a5b037@Dell>
Dear Ralf,

I also thank you for the reply.

> On Wed, May 12, 2021 at 12:04:36AM +0200, Nagy Gabor wrote:
> > 2. Can I do logical OR operation on database filtering, concerning
> > different properties?
> > For example, I want to list issues with "assignedto=15 OR actor=15".
> > Do we have a built-in query for this, or shall I utilize
> > filter_sql, or any other custom solution?  
> 
> As John has already written, this is currently not possible using the
> roundup API. What you *can* do is an explicit SQL query using
> db.sql(...).
> 
> > 3. This one is a little more general. I know that relational
> > databases are not designed to store lists/arrays. But I have to
> > implement somehow a property (let's call it "important_dates")
> > which stores a LIST of dates. What is the best practice to
> > implement this?  
> 
> I would put that in a separate class with a Link property to the class
> where you need that list of dates. Lets call that class 'issue' (but
> it doesn't need to be the issue class for this example). If you need
> to navigate from a node of the issue class to the list of dates you
> can produce an automagic multilink property in the issue class using
> 'rev_multilink' parameter in the important_date class in the Link
> definition.

My only concern about rev_multilink (in general) is whether I can easily
edit links of properties of a class different from the actual context.
(For example, if I am in context issue1, than I might have to edit the
Link property of date324.) But I will play with @link@ and @remove@
commands, and it will turn out.

Regards,
Gábor

> Ralf


_______________________________________________
Roundup-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/roundup-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.