I am planning to generate a dc js crossfilter object in one page and use it across multiple pages; is there a way to serialise and store the crossfilter object in local storage and reuse it?
Thanks,
Arun
Related
I have backend API that have group of methods that retrieves some data series for charts in web/mobile apps from database by different sql-queries.
Some data series uses as-is, another - calculated from reteved data series.
At this time I have Controller that call Repository. And if I need to calculate data then I pass data to math function and get another series.
And I am stuck in how to clearly organize my code. What design-patterns to use? How to separate code?
pls, help :)
I'm currently using DexieDB to store data in 10 different collections.
When a user is navigating to a single page, I collect data from these 10 different collections as the data source.
The main collection has an identifier that is being used to get the corresponding data from the other collections.
With the new liveQuery update I managed to get this working for a single collection, but I was wondering if I were to use it for multiple collection what the best approach would be.
Would it be better to create multiple subscriptions for the collections that need to be watched (not all of them), or would it be possible to create 1 subscription over multiple collections?
I looked in the docs, but all the examples include only one collection, and there isn't any documentation on how this would work with multiple collections.
Thank you in advance!
Both ways are possible. If you are in a Component based GUI framework (React, Angular, Svelte etc), one subscription per query is normally what to prefer becuase by splitting it so, a mutation affecting the query on the related collection will only trigger a re-render of its component instead of re-rendering also its parent.
That said, you can also perfectly well perform multiple queries within your callback to liveQuery and return an array or object containing the data. That way you will implicitly subscribe to all the visited queries.
I keep doing google of how to store object data in Laravel.
I have an Model object which is using among functions and the Model data will not be changed indeed. So I want to store it into the global area for access.
I think it should be stored in something like the ServletContext(Application Scope) in tomcat. But I can't find such concept in Laravel at all.
Could anyone help?
Thanks!
If you want to store it for the current session, just store it in session. That will be the easiest way to share it between methods.
I am validating the data from Eloqua insights with the data I pulled using Eloqua API. There are some differences in the metrics.So, are there any issues when pulling the data using API vs .csv file using Eloqua Insights?
Absolutely, besides undocumented data discrepancies that might exist, Insights can aggregate, calculate, and expose various hidden relations between data in Eloqua that is not accessible by an API export definition.
Think of the api as the raw data with the ability to pick and choose fields and apply a general filter on those, but Insights/OBIEE as a way to calculate that data, create those relationships across tables of raw data, and then present it in a consumable manner to the end user. A user has little use with a 1 gigabyte csv of individual unsubscribes for the past year, but present that in several graphs on a dashboard with running totals, averages, and timeseries, and it suddenly becomes actionable.
I have 3 dc.js charts on my page. I would like to make the data it consumes as dynamic as concurrent users might range from 5 to 15 users. If I use .CSV and .JSON, the physical file needs to be created on server and concurrency would be an issue. Is there a way to pass in-memory data to d3.js for rendering the charts? Any example/help is appreciated.
Thanks
BV