Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 3 of 3 total
Thread LoadFromStream() fails because the cursor is read only
Sat, Jul 20 2013 1:43 PMPermanent Link

Arno Garrels

Hi,

I'm currently trying to port a DBISAM application to ElevateDB.
In DBISAM it was possible to do a LoadFromStream when the result set of the query was a join of multiple tables.
In ElevateDB this does not seem to work since the LoadFromStream method raises an exception (read only cursor).

Is this a bug or "as designed"?

Regards,
Arno Garrels
Sun, Jul 21 2013 3:39 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Arno

>I'm currently trying to port a DBISAM application to ElevateDB.
>In DBISAM it was possible to do a LoadFromStream when the result set of the query was a join of multiple tables.
>In ElevateDB this does not seem to work since the LoadFromStream method raises an exception (read only cursor).
>
>Is this a bug or "as designed"?

I've not tried it but I'd guess its by design. In DBISAM queries were editable (sensitive in ElevaeDB speak) unless you asked for canned. In ElevateDB queries with JOINs are insensitive (ie canned) and can't be made sensitive (ie live) so it would make sense to prevent something that is read opnly being copied to something that is read/write.

If I'm correct then the only way I can see round it is to create a temporary table (CREATE TEMPORARY TABLE xxx AS query) and stream that to a table component.

Roy Lambert [Team Elevate]
Sun, Jul 21 2013 8:33 AMPermanent Link

Arno Garrels

Roy,

> If I'm correct then the only way I can see round it is
> to create a temporary table (CREATE TEMPORARY
> TABLE xxx AS query) and stream that to a table component.

Thank you very much! Works fine.

--
Arno
Image