May 21, 2021 at 6:05 pm
The information_schema is an ansi standard for SQL metadata supported by every DBMS. So the format for representing SQL data is standard.
No the basic syntax for describing the structure of the data is a standard, ignoring that pretty much all platforms have their own specific DDL additions. And how it is actually stored and transmitted is not at all standard.
For example if I gave you this DDL,
CREATE TABLE MYTABLE(COL_ONE varchar(300), COL_TWO varchar(300), COL_THREE varchar(300));
And this chunk of data fdFkjsfacbvnVxcmbvmnadsvsvAcvbxcm123nvmbAxcv,mnxvnakljklvvakljkljljl
With no additional information can you parse it out into rows and columns?
May 21, 2021 at 6:14 pm
And how it is actually stored and transmitted is not at all standard.
Well of course not, the whole point of the relational model is that you don't have to know how the data is stored, you only need the logical interface to the data.
As for your example, if you provide the logical interface then of course it can be interpreted. If, for example, you send someone a SQLite file, then the metadata, data and the logical interface are all delivered in the same package.
10 years ago XML was going to solve all our problems, now JSON is in fashion, how long before all the JSON people are currently using has to be replaced by the next trend?
May 21, 2021 at 6:50 pm
And how it is actually stored and transmitted is not at all standard.
Well of course not, the whole point of the relational model is that you don't have to know how the data is stored, you only need the logical interface to the data.
As for your example, if you provide the logical interface then of course it can be interpreted. If, for example, you send someone a SQLite file, then the metadata, data and the logical interface are all delivered in the same package.
10 years ago XML was going to solve all our problems, now JSON is in fashion, how long before all the JSON people are currently using has to be replaced by the next trend?
Okay but the theoretical interface you are proposing doesn't exist in any shape or form right now. JSON may be replaced by something soon enough maybe by what your suggesting. But we're not talking about theoreticals here, we're talking about the real world situation and JSON exists what you are talking about does not.
And for some of the reasons I already explained is not in fact better than JSON or whatever across the board since you're creating a larger more complicated pay load that is simply not necessary for everything.
Viewing 3 posts - 31 through 32 (of 32 total)
You must be logged in to reply to this topic. Login to reply