Discussions
Categories
- 197K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.8K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 556 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.4K SQL Developer
- 296.3K Development
- 17 Developer Projects
- 139 Programming Languages
- 293K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 158 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 468 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
Initializing.... state in ojTable and why

I am coding a simple view HTML with a "main" table on the left and a subtable on the right.
When one row of the main table is selected, data is fetched from the backend, using the row's id - such data fetched "on demand" as the selection changes populates the sub-table (on the right) - There is just 1 subtable, its content gets replaced as selection changes.
The problem is that sometimes I see the content of the right table (when the page is just loaded, so no row has been selected) as
<HEADER1>, <HEADER2>, ...
Initializing... |
other times I see
<HEADER1>, <HEADER2>, ...
No data to display
When the latter happens, it's fine: when I will select the row of the main table, I will see the other populated
When the former happens, no data will ever be showed in the sub-table ever (even if the back-end is called and data is processed by the viewModel). I have to press F5 again and again until it goes away. Roughly, 3/4 of the times is 'No data to display'
Could anyone explain what these statuses mean and what they imply in terms of underlying data? What is happening to make 'Initializing...' appear instead of 'No data to display' ?
I don't think it's important, but the sub-table is populated in this way:
self.primaryTableSelectionListener = function(event,ui) { // update the current ID doDashboardDetails(CURRENT_ID)}this.data = ko.observableArray();this.ds = new oj.ArrayTableDataSource(this.data, {idAttribute: 'id'});dataFetched.subscribe(function(tableData) { this.data(tableData);}, this, "ps");function doDashboardDetails(CURRENT_ID) { $.getJSON("/stats/"+CURRENT_ID). then(function(ep) { tempArray.push({ ... }); tempArray.push({ ... }); tempArray.push({ ... }); dataFetched.notifySubscribers(tempArray, "msg");
});}
Answers
-
Hi,
At a very high level, the "Initializing" means that it's trying to get the data still, while the "No data" is shown after the REST call is completed and there is no data returned.
Usually if the "Initializing" message is shown for an extended period of time, then your REST call has failed for some reason.
I'm a bit confused about why you are using the publish and subscriber method in this and not the existing event methods that come with the oj-table. I'm sure that is just my lack of knowledge on what you are trying to do.
Hope that helps