Re: $where and Maximo

[Chris Snow <chris_snow@EMAIL.MSN.COM>]

Aha!  Thanks for the clarification.  I can see a potential problem with
ambiguous column references if someone is using the $where along with a
table join.  If the joined table contains column names the same as that of
the one in the $where statement, then it would be important to use the full
tablename.columnname definition.  If you look at the prm file in the SPL
directory you'll see that Maximo builds it with a full reference for all
tables and columns.


-----Original Message-----
From: Wanko, Christopher <cwanko@GRENET.ATT.COM>
To: Multiple recipients of list SQR-USERS <SQR-USERS@list.iex.net>
Date: Monday, May 11, 1998 10:03 AM
Subject: Re: $where and Maximo


> There are several of us out here who write for Maximo.  Please give an
> example of shortened tablenames as you are using them.

I think he means a problem with this:

from max_db.dbo.workorder
where max_db.dbo.workorder.wonum > '0092000'
and max_db.dbo.location not null

whereas SQL has no problem with the following,
assuming your database is currently max_db:

from workorder
where wonum > '0092000'
and location not null

Since I'm a vocal SQR/ MAXIMO warrior (who hasn't won a battle yet
without
some scarring and unstaunched bleeding), I can attest that MAXIMO really
likes the full qualifications, but I have reports that work without it.

Version matters.  I use SQR Workbench 3.5, and other versions may not
work the same.  I'm also using MAXIMO rel 3.0.2 for Sybase, so again
mileage may vary.  Offer void in Tennessee.

-Chris