-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Your assumption is correct. There is no workaround at present except to simply not have filter option values with commas in, which is obviously not always possible.
It's on our list of things to fix. Arek should be able to give you an idea of when it might be done. cheers, Richard Dr Rob Free wrote: > Hi > > I'm having a problem with data that contains commas. > > When I make a filter option (qualifier '=' or 'like') with commas in it > (using MartEditor), and select it in MartView it appears as a 'SELECT.. > FROM.. WHERE IN' statement in the SQL log (separated by space). However, > I get the correct statement when I select an option with no commas in > from the same filter. > > The Perl and XML generated through the buttons also include the > individual IN items. > > From this, I assume that BioMart uses the presence of commas as a signal > to create an IN statement and split the string at each space. Is there a > work-around to stop this happening? > > Thanks for your help > > Rob > - -- Richard Holland (BioMart) EMBL EBI, Wellcome Trust Genome Campus, Hinxton, Cambridgeshire CB10 1SD, UK Tel. +44 (0)1223 494416 http://www.biomart.org/ http://www.biojava.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHZ6x24C5LeMEKA/QRAgYXAJ4lYng2PcnmnbRqX+RUKHE0+WMKYgCglVHq WUJLqsmgDRxGfbVkWXRGdLE= =gq3m -----END PGP SIGNATURE-----
