Code: Select all
oracleDataTable.MissingSchemaAction = MissingSchemaAction.Add;
Code: Select all
oracleDataTable.MissingSchemaAction = MissingSchemaAction.Add;
Code: Select all
oracleDataTable.CancelFetch();
The reason is that asynchronous reading returns control to your code immediately. It may seem that data are fetched quickly. But the data are actually fetched in another thread.lewis wrote:the problem with Fillpage method is slow
The issue occurs when you call the BeginFill method after calling CancelFetch. If you replace CancelFetch with SuspendFill, the reading will continue starting from the place where it stopped. However, if you call the BeginFill method after all the table was already read till the end, the method initializes reading since the beginning. If your table has a primary key, that won't do any harm. But if not, the records, read again from the beginning of the table, will be added to the table. This is why we advise you to add a check whether the number of rows in the DataTable is equal to the number of the corresponding rows in the database.lewis wrote:Hi, I thought before to make this "before query", the problem is
We are using FillPage in dbForge Studio for Oracle. https://www.devart.com/dotconnect/oracl ... nt32).htmllewis wrote:My question is how dbForge Studio for Oracle did by using "Go to next Page" button.