Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 23 APR 2003 01:06:26PM [email protected] wrote:

I find this odd .. a developer came to me with this .. maybe someone here can explain this

they wanted to select all the tables with a specific volume which didnt have a secific MFS on it. so they did ..

select systables with volume=myvol' and filesystem # containing "x_mfs"

It returned back all tables. yes .. even those with the mfs.

so since filesystem was mv we tried exploding .. that worked BUT we still couldn't select/in or out those tables with the mfs.

we tried a lot of little things .. but nothing worked.

They have fallen back on writing a routine to do it BUT

Why would this be?

[email protected] onmouseover=window.status=the new revelation technology .. a refreshing change;return(true)"

David Tod Sigafoos ~ SigSolutions

Phone: 971-570-2005

OS: Win2k sp2 (5.00.2195)

OI: 4.1.2


At 28 APR 2003 10:37AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

How's about something like

LIST FILES FILING.SYSTEM WITH EACH FILING.SYSTEM # 'QUICKDEX.MFS' AND WITH VOLUME.NAME 'SAMPLE_VOL'

from an ARev 2.1 system….

The Sprezzatura Group

World Leaders in all things RevSoft


At 28 APR 2003 02:07PM John Bouley wrote:

The reason for this I think is because filesystem is multivalued. Remember if you were to select on a multivalued field any value equal would include the record. Well if you say any value not equal then the other value would always be not equal thus including the row. I think the containing just complicates matters more. At least that is how my theory goes….

HTH,

John Bouley

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/ea47ce244b2d522185256d11005df90a.txt
  • Last modified: 2024/01/04 20:57
  • by 127.0.0.1