Difference between Package and View

[Tehila1]

I use the built-in search for getting checked-out packages for me.  

It works fine for checked out packages, as opposed to checked out view;
a checked out view doesn't appear in the search result unless there is currently  also a checked out package in the model.

 Have someone encountered this bug?

[qwerty]

Could you post your SQL? I don't think there's a big difference between view and package.

q.

[Tehila1]

Could you post your SQL? I don't think there's a big difference between view and package.

q.

The SQL I copies from the built-in search for checked out packages:  

Code: [Select]

SELECT
t_object.ea_guid AS CLASSGUID, t_object.Object_Type AS CLASSTYPE,t_object.Name AS Object, t_object.Object_Type AS [Type], t_object.Stereotype, t_object.Scope,t_object.Status, t_object.Phase, t_object.CreatedDate, t_object.ModifiedDate
FROM
t_object, t_package
WHERE
t_object.Object_Type='Package'
AND
#DB=Other#t_object.PDATA1 = cstr(t_package.Package_ID)#DB=Other#
#DB=ORACLE#t_object.PDATA1 = to_char(t_package.Package_ID) #DB=ORACLE#
#DB=OPENEDGE#cast(t_object.PDATA1 as char(25)) = cast(t_package.Package_ID as char(25))#DB=OPENEDGE#
#DB=ASA#t_object.PDATA1 = cast(t_package.Package_ID as char)#DB=ASA#
#DB=SQLSVR#t_object.PDATA1 = cast(t_package.Package_ID as char(25))#DB=SQLSVR#
#DB=MYSQL#t_object.PDATA1 = t_package.Package_ID#DB=MYSQL#
#DB=POSTGRES#t_package.Package_ID = t_object.PDATA1::text::int#DB=POSTGRES#
AND
t_package.PackageFlags LIKE '#WC#VCCFG=#WC#CheckedOutTo=#UserName##WC#'
Something wrong?

[qwerty]

I just tried that query and it returned package as well as view. Which RDBMS are you using?

q.

[Tehila1]

I just tried that query and it returned package as well as view. Which RDBMS are you using?

q.

The model is Oracle based.
Did you try the query in case there are only view checked out, with no package?

[qwerty]

Yes (once you said it). And the result is still correct. I don't have Oracle (just using EAP) so someone else would need to verify that. Anyhow, I would not see why Oracle would not work wrongly as opposed to other RDBMS. Maybe you could send a bug report. I suppose there is another reason for the behavior. Sparx support is quite helpful when it comes to such issues.

q.