best practices
Quote from Phil78 on January 7, 2022, 6:53 pmHello, I have a structure with 3 tables master/detail like continent/country/ town with less than 1000 records for the last level.
I would like to know if the best choice is to use a database or a JSON file to store the data with visualneo web ?
If it is JSON, is it better to have one big JSON or one JSON per level ?
thanks in advance for your answers.
Hello, I have a structure with 3 tables master/detail like continent/country/ town with less than 1000 records for the last level.
I would like to know if the best choice is to use a database or a JSON file to store the data with visualneo web ?
If it is JSON, is it better to have one big JSON or one JSON per level ?
thanks in advance for your answers.
Quote from AsleyCruz on January 8, 2022, 7:26 amHi @phil78
If your records won't be too big, you can use JSON and try to use pagination to load records 20 by 20, 40 by 40, or whatever. This is good to load records very fast.
Use pagination too if you decide to use database. Well, this is my preference.Happy coding!
Hi @phil78
If your records won't be too big, you can use JSON and try to use pagination to load records 20 by 20, 40 by 40, or whatever. This is good to load records very fast.
Use pagination too if you decide to use database. Well, this is my preference.
Happy coding!
Quote from Phil78 on January 8, 2022, 3:43 pmthanks @asleycruz I will take your advice, I guess LoadAsyncJSON handles the pagination because I don't have the hand to do it...
thanks @asleycruz I will take your advice, I guess LoadAsyncJSON handles the pagination because I don't have the hand to do it...
Quote from Gaev on January 8, 2022, 7:34 pm@phil78
You can use neoTable to display the rows/columns ... it has built in Pagination ... and it accepts JSON as input (which can be output from neoCms).
You can use neoTable to display the rows/columns ... it has built in Pagination ... and it accepts JSON as input (which can be output from neoCms).