A problem with the new version and oracle packages

[enigma51]

Hi
The new version of linq connect /oracle connect has an issue when it comes to calling packages.

I have application that calls two procedures (in one package) one for update and one for insert

If I stop the app on insert i can see the record in the db if i continue the record gets removed from the database.

Also records that are in the database are not being returned when doing a where query after i run the package

Yet if i reinstall the old version 11 aug every thing works as expected.

[enigma51]

you guys are realy quick with repsonse arent you?

[StanislavK]

Could you please describe the issues in more details? For example, please specify the following:
- what exactly the update and insert procedures do;
- how do you determine that the row is or is not in the database (e.g., via a standard tool, or by executing a LINQ query);
- describe the query that does not return the proper result set.

If possible, please send us the scripts needed to create the database objects and/or a complete small project with which the problems can be reproduced.

As for the reply delay, we have a two-business-day response policy, though do our best to reply as soon as possible.

[enigma51]

The insert is very simple

Package is as follow

PROCEDURE New_Err_MonRow(in_ErrMsg IN errmonitor.errmsg%type,
in_CreatedBy in errmonitor.createdby%type,
in_MaxCreatedDate in errmonitor.maxcreateddate%type,
in_MinCreatedDate in errmonitor.mincreateddate%type,
in_NumberOfIssues in errmonitor.Numberofissues%type)
AS
NewId number;
BEGIN
select errmon_id_seq.nextval into NewId from dual;
insert into errmonitor (id,
errmsg,
createdby,
maxcreateddate,
mincreateddate,
numberofissues,
Errstatus)
values (NewId,
in_ErrMsg,
in_CreatedBy,
in_MaxCreatedDate,
in_MinCreatedDate,
in_NumberOfIssues,
1);

commit;
END New_Err_MonRow;

PROCEDURE Update_Err_MonRow(in_Id in errmonitor.id%type,
in_ErrMsg IN errmonitor.errmsg%type,
in_CreatedBy in errmonitor.createdby%type,
in_MaxCreatedDate in errmonitor.maxcreateddate%type,
in_MinCreatedDate in errmonitor.mincreateddate%type,
in_NumberOfIssues in errmonitor.Numberofissues%type,
in_Status in errmonitor.Errstatus%type,
in_Comments in errmonitor.comments%type)
AS
str_Comments errmonitor.comments%type;
BEGIN
if(in_Comments = '')
then
str_Comments := null;
else
str_Comments := in_Comments;
end if;



update errmonitor set errmsg = in_ErrMsg,
CreatedBy = in_CreatedBy,
MaxCreatedDate = in_MaxCreatedDate,
MinCreatedDate = in_MinCreatedDate,
NumberOfIssues = in_NumberOfIssues,
ErrStatus = in_Status,
Comments = str_comments
where id = in_id;

commit;
END Update_Err_MonRow;
END ErrMon_PKG;


The rows are in the db when i run a sqlplus query but if i continue with the app the rows are disappearing

Also for some reason the linq query on first run doesnt find any rows. It only finds the rows that are "inserted" when the application is run.

The strange bit is that the previous version doesnt have any issue's

I should also point out that this is not a new app it was initialy created when devart started with the linq to oracle. The only changes has been to use the newer libaries. It was our first look at how we can use linq hence the very simple package.

[StanislavK]

Please specify what exactly you mean saying that the inserted rows disappear, and describe the query that finds no rows. I will send you a sample project, please specify what should be changed in it to reproduce the mentioned issues.

[enigma51]

Please specify what exactly you mean saying that the inserted rows disappear, and describe the query that finds no rows. I will send you a sample project, please specify what should be changed in it to reproduce the mentioned issues.

To replicate the issue we need to install the new version again. At the moment we are in the middle of a project and cant spend the time installing and uninstalling.

I think the cause of the issue might be because we build the first "model" with the older linq connect and havent change it since. Only upgraded the dll's and made some form changes.

I was going to destroy the entity model and recreate it from the DB but it will have to wait a while.

[enigma51]

Did some tracing on this.

The packages was called twice for somereason. But the good news is that the new version has fixed the issue

[StanislavK]

Glad to see that the problem was resolved.