Thursday, December 11, 2014

Happy Holidays!





To all my readers and colleagues, Happy Hanukkah, Merry Xmas and a healthy, prosperous and Happy New Year!!!!

Sunday, December 7, 2014

Weekly Update



1. Quote of the Week
Relational is/was a way for humans to understand how computers could organise data. From a day back when disks were expensive. --LinkedIn.com

2. To Laugh or Cry?
How Google Will Use Firebase to Supercharge Its Cloud Computing
Another reinvention of a (square) weheel.


3. Online debunkings
Calendar supertype

4. Interesting elsewhere
On Persistence and Data Management
An oldie but goodie; check out my comment.


5. And now for something completely different

Fascinating:
John Cleese on the Black Knight and Douglas Adams' High Heels

About The PostWest:
White House exempts Syria airstrikes from tight standards on civilian deaths
Remember all the fuss about Israel not doing enough to prevent civilian deaths? The hypocrisy!




Wednesday, December 3, 2014

Analytics & SQL Tables



My December blog @All Analytics. 

Manipulating/extracting data from SQL databases and interpreting results without knowledge of what the source tables mean is almost certain to lead analysis astray. To ensure sensible analysis and properly interpreted results, the conscientious analyst may have to do some digging that requires basic database knowledge. Here's why.

Read it all. (Please comment there, not here)








Sunday, November 30, 2014

SQL's Incomplete Set-lization, Part 2




by Erwin Smout


[FP: Two weeks ago I posted a debunking of an article blaming some SQL sins. Erwin has some additional comments.]

1. Multisets


From the original article:
It is beyond any doubt that set is the basis of mass data computation. Although SQL has the concept of set, it is limited to describing simple result set, and it does not take the set as a basic data type to enlarge its application scope.
Sidestepping several possible nitpicks here, such as e.g., that SQL allows duplicate rows and thus, in its basic form, has bag, not set algebra, the intention behind the complaint here is mostly accurate.

Sunday, November 23, 2014

Weekly Update UPDATE 2



Housekeeping: I have added a link to Nijssen's paper The Entity-Relationship Model Considered Harmful to FUNDAMENTALS on the HOME page. UPDATE 2: The paper is fine if read with a PDF viewer other than
Adobe Reader XI (11.0.09).


1. Quotes of the Week
Platfora’s mission is to empower customers to transform their businesses into fact-based enterprises. Platfora's Big Data Analytics Platform masks the complexity of Hadoop, making it easy for customers to understand all the facts in their business... --Platfora.com
Q: I don't know what the different between detect inference in database and prevent it, any help?
A: Why would you want to prevent inferences that a DMBS makes? That's where the power of it is. --LinkedIn.com
2. To Laugh or Cry?
Graphs: A Better Database Abstraction
3. Online debunkings

4. Interesting elsewhere
You Too May Be A Victim Of Developaralysis
H/t Will Sisson.

5. And now for something completely different 
  • About The PostWest
If they do this:
Fatah official calls for blood to 'purify' Jerusalem of Jews
PA airs 'anti-Semitic' film as tensions mount in Jerusalem
Four killed in terror attack at Jerusalem synagogue
then obviously we should do this:
Croatia likely to recognize Palestine as a state MidEast
Sweden To Recognize State Of Palestine
Spanish Parliament Calls on Rajoy to Recognize Palestine
UK lawmakers vote to recognize Palestine as a state
and this
EU threatens 'further action' to protect two-state solution
EU considering 'sanctions' against Israel over settlements
Makes perfect sense. So what else is new?



Friday, November 7, 2014

Relational Fidelity and Analytics Integrity




My November blog post @All Analytics:


I have shown in previous posts that reliance on sheer visual inspection of database tables for data analysis is a risky proposition, with high probability of misinterpretation. All the more so when databases are complex, with wide and/or long tables. The analyst needs to know table interpretations -- their real-world meaning derived from the business rules with which the database must be consistent. The problem is that they are left out of the tables because DBMSs do not understand them, nor are they usually documented in the database (as they well should be), because database professionals underestimate their importance.

Read it all. (Please comment there, not here)









View My Stats