Earlier quoted context omitted.
The article describes why. 2 different db engines (or even instances) can use different file layouts for the same schema. In many was sql is all about divorcing the schema from the files.
But on the other hand, in all database systems the schema is used to determine how the files are laid out. Although I suppose the same thing could be argued for any data that is stored in a file, excepting that a schema is metadata that determines the organisation of data so it's a bit of a special case.
I Went to SQL Injection Court
61–70 of 463 posts
Re: I Went to SQL Injection Court
#62Is it not absurd that the supreme and appeal courts disagreed on a syntactical matter? Never mind that this isn't uncommon, or that (IMHO) it would be ridiculous to interpret it as "any file layouts at all, and other stuff too, but only bad other stuff". It's crazy to me that were happy for laws to sit on the books being utterly ambiguous. I know this suits the courts who benefit from the leeway, and that (despite va…
To me it feels like the kind of dispute that is exactly why we have multiple levels of appeals court. The "file format" thing is super dumb, and they got it wrong, but the "that if disclosed" statutory interpretation is a thing that seems important to get a final, consistent determination on.
Even (some) programmers have learnt the dangers of parsing at run time (e.g. "eval is evil"). How can we decide it's the law we want if we don't know what it means yet?
Re: I Went to SQL Injection Court
#63Earlier quoted context omitted.
What are the administrators of CANVAS hiding?
Hard to say. One of my personal drivers for this lawsuit is a tip I received that said that Chicago has a list of vendors whose tickets are dropped in the back-end. When I requested that info, the city said they had no such list. I trust my source, so having schema information could help figure out the extent and if they were lying.
Re: I Went to SQL Injection Court
#64Earlier quoted context omitted.
Yep, that was done in the FOIA request related to this lawsuit: select utc.column_name as colname, uo.object_name as tablename, utc.data_type as type from user_objects uo join user_tab_columns utc on uo.object_name = utc.table_name where uo.object_type = 'TABLE' https://www.muckrock.com/foi/chicago-169/canvas-database-sch...
Yeah, it's obvious the double standard here, then. Curious indeed why they are so adamant to keep the schema/data secret.
Re: I Went to SQL Injection Court
#65I sure hope the impact of this is not that government entities switch to schema less databases!
Re: I Went to SQL Injection Court
#66Earlier quoted context omitted.
How is a database schema not a file layout?
The article describes why. 2 different db engines (or even instances) can use different file layouts for the same schema. In many was sql is all about divorcing the schema from the files.
Re: I Went to SQL Injection Court
#67Anyone with a legal background willing to opine about potential workarounds to this ruling? Specifically, would a request for “data field labels” (i.e. a column list without any table structure info) likely circumvent the exemption?
Re: I Went to SQL Injection Court
#68Earlier quoted context omitted.
The article describes why. 2 different db engines (or even instances) can use different file layouts for the same schema. In many was sql is all about divorcing the schema from the files.
There's a solid chance that the schema gives away what DBMS is being used. But even if it didn't, I'd still call it a file layout in this context.
Re: I Went to SQL Injection Court
#69Earlier quoted context omitted.
The article describes why. 2 different db engines (or even instances) can use different file layouts for the same schema. In many was sql is all about divorcing the schema from the files.
There's a solid chance that the schema gives away what DBMS is being used. But even if it didn't, I'd still call it a file layout in this context.
Re: I Went to SQL Injection Court
#70Earlier quoted context omitted.
How is a database schema not a file layout?
It literally does not describe a file, and does not literally describe the data layout of anything on disk (though with enough knowledge, you may be able to infer facts about probable layouts).
Huh? Depends on the DMBS, but each InnoDB table is a file.
And the schema determines the file structure.