> Is this definitely to do with the double slashes rather than the colon?
Thanks for sending me back to the testing bench. Actually it's neither. (!)
It's the trailing single slash at the end of the object name.
The following causes the problems in sgifaceserver and tace that I reported
acedb at www.graingenes.org> find reference bob/
1. The problem occurs whether "bob/" is in the database or not.
2. The following variations work fine (including give the correct results
if the object is in the database):
acedb at www.graingenes.org> find reference bo/b
acedb at www.graingenes.org> find reference "bob/"
acedb at www.graingenes.org> find reference "bob\/"
acedb at www.graingenes.org> find reference "bo/b"
acedb at www.graingenes.org> find reference "bo\/b"
3. The following variations don't cause the server to crash, but they don't
find any objects:
acedb at www.graingenes.org> find reference bob\/
acedb at www.graingenes.org> find reference bo\/b
Apologies for not analyzing the problem properly in the first place.
> From krb at sanger.ac.uk Tue May 13 03:59:00 2003
> To: bionet-software-acedb at net.bio.net> Subject: Re: problem with object names containing "//"
>> On 6 May 2003, Dave Matthews wrote:
>> > Big problem with sgifaceserver, smaller with tace.
> > % saceclient www.graingenes.org -port 2000
> > acedb at www.graingenes.org> find reference http:/\/maswheat.ucdavis.edu/protocols/BYDV/
> > No response. The server crashes after a few minutes. During which it
> > uses a lot of cpu and memory, sometimes all of the memory.
> > "find reference http*BYDV*" has no problem, works fine.
> > In tace there's no performance problem, the "acedb>" prompt returns
> > immediately. However there's no report of the result, not the expected
> > "// Found <xx> objects in this class". And nothing was found.:
> > acedb> find reference http:/\/maswheat.ucdavis.edu/protocols/BYDV/
> > acedb> list
> > // Found 0 objects in this class
> > // 0 Active Objects
> > This is with ace4_9p on Solaris 8. (Which otherwise is working fine,
> > http://www.graingenes.org.)
>>> Hi Dave,
>> Is this definitely to do with the double slashes rather than the colon? I
> seem to recall some problems in the past with making queries that would
> accept colons. Maybe this is unrelated.
>> ~ Keith Bradnam - WormBase group: http://www.wormbase.org/> ~
> ~ The Wellcome Trust Sanger Institute,
> ~ Hinxton, Cambridge, CB10 1SA, UK. Tel: 01223 494922