Infralution Support Forum Index Infralution Support
Support groups for Infralution products
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Getting around apparent recordset size limitation

 
Post new topic   Reply to topic    Infralution Support Forum Index -> Virtual Data Objects Support
View previous topic :: View next topic  
Author Message
MikeR



Joined: 25 Jun 2016
Posts: 28

PostPosted: Thu Aug 17, 2017 9:30 pm    Post subject: Getting around apparent recordset size limitation Reply with quote

Using VT4 and VDO against a 64 bit PostgreSQL 9.6 server with 32 bit app and 32 bit official postgresql odbc driver installed and hooked to VDO virtual connection. Using adClient cursors. Other properties defaulted.

I am doing stress testing against VDO and VT4 for an application that requires possibly large datasets. I loaded a table with 5 million records for this test, to see what the VT would do with it.

I have a VirtualRecordset descendent composed of VirtualRecord descendents based on my database schema. The code follows the sample programs closely and appears to operate correctly in all other details.

My query is simple, SELECT * FROM MYTABLE;
The sorting is against a column that is not the primary key but another text info that can be in a different order than the primary key, and I want to keep the sort order based on that different column. If this is an issue, please let me know. I don't think it is. If I change it to match the primary key, not much different happens.

What I am finding is that the recordset loads (takes about 20 sec) and sets the Count at 84796, which is a mystery since it should be 5 million. When the tree shows rows visible, I see only the last 84793 or so records with record number 4999999 at the bottom. If I reverse the sort, I see 0000000 at the bottom and back with a total of 84792 records or so. VT uses the count apparently correctly, so I don't think VT is the bad boy here.

I am trying to figure out what is at fault, VDO, ADO, ODBC, or PostgreSQL server. Anyone have any clues or a possible workaround, please let me know. This is a show stopper for us until we get this sorted out.

Thanks.
_________________
Thanks,

-- Mike R.
Back to top
View user's profile Send private message
Infralution



Joined: 28 Feb 2005
Posts: 4884

PostPosted: Sat Aug 19, 2017 12:30 am    Post subject: Reply with quote

I think the most likely culprit here is the PostgreSQL ODBC/ADODB driver. I've just modified the Virtual Tree DatabaseBrowser sample to create over a million vehicle records. It loads these without any problems using either client or server side cursors and Virtual Tree displays them correctly.
_________________
Infralution Support
Back to top
View user's profile Send private message Visit poster's website
MikeR



Joined: 25 Jun 2016
Posts: 28

PostPosted: Sat Aug 19, 2017 5:17 pm    Post subject: That narrows it down Reply with quote

Thanks, that helps. More news as it happens.
_________________
Thanks,

-- Mike R.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    Infralution Support Forum Index -> Virtual Data Objects Support All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group