If you have come from a RDBMS background the simplest way to imaging the difference between fields and tags is to see the fields as columns, and a tags as a indexed columns. You should be very careful with the combination of tags, ensure they are limited to avoid high cardinality: Although you can join tables based on tags, if you are doing this its usually very ineffcient and you should consider your schema design Indexes Influx doesn’t really support this concept. You can also see in purple the tags “firstName” and “lastName” flux language splits the data into tables (see column 1) on each change of the combination of tags Foreign keys Designed for developers and data analysts. Download DbSchema for Windows to design, implement, and edit SQL queries of your database. A free, simple tool to draw ER diagrams by just writing code. If you see the two columns highlighted in red you notice that instead of a bill being displayed as a single column, its actually seen as two columns _field and _value Draw Entity-Relationship Diagrams, Painlessly. You will notice that all the the data is presented as a table, the interesting point to note is that its not a table in the traditional sense with columns and rows, its more a list of meta data around a single field: The editor comes with syntax highlighting and. For further database analysis, you can take advantage of the built-in SQL editor to write and execute scripts. In addition, DbSchema also offers you the possibility to work with diff scripts. So the data actually comes out like this: DbSchema integrates schema comparison tools that can be used to analyze the differences between databases. However Influx stores its data as a point in time with associated tags (2 of those tags being field name and measurement). If you were to think of this data in a normal RDBMS it would come in a table like this: Date
0 Comments
Leave a Reply. |