I was just assigned to update the old website, and I can move it from the old archaic system to drupal. The only problem is that it stores the real estate system and a lot of data. Currently, all information is stored in one table, the identifier is a house, and then everything else is a key / value pair. There are 243 keys per property, in the system 23840 units. As you can imagine, the system is slow and complex to query.
I do not think that a table with 243 rows would be a very good idea and probably worse than the current situation. I did some investigation, and here is what I found out:
- , , , /.
?
Estate n - 1
1--1
1 - n
(dynamic?) id/key/value
- , , . , , , , , .
, differnt (, , , , , , ), 20% . null.
, , , , . XML- , , ?
. , , 1-1, . - , . JUst , .
-. , , . suck .
Source: https://habr.com/ru/post/1749604/More articles:php shell_exec executing java program - javaPHP shell_exec () command not working for my custom Java application5 - javaGetting total hours in TimeSpan - c #to create sparse BufferedImage in java - javaLatex: table of contents for section only - latexProblem printing print google maps and using page break before in IE8 - javascriptWhat are the pros and cons of the option to "include external columns in the model" in EF 4 - visual-studio-2010Создать Java-метод из строки? - javaIs there a tool that will create Java or .NET classes from a db4o database file? - db4oRich text editor for JSF 2 - javaAll Articles