News for hackers. Stuff that matters.

A comment on Write code. Not too much. Mostly functions.. Parent comment

Re:Write code. Not too much. Mostly functions. by bob1029 on Monday December 21, 2020 @09:24PM (#25502188)
I think you may underestimate the potential scope of a domain model and the capabilities of SQL. It is certainly math. That is actually the incredible part. That its all just math underneath 20 different joins which express a very complex and meaningful view of the domain facts.

I challenge anyone to present a problem domain which cannot be meaningfully represented in terms of tables in a database. I would prefer if this were bounded by the set of problems you would use any software development strategy upon, but I welcome a more difficult problem as well.

[ Parent | on HN ]
Re:Write code. Not too much. Mostly functions. by FpUser on Monday December 21, 2020 @09:52PM (#25502350)
>"I think you may underestimate the potential scope of a domain model and the capabilities of SQL."

I am being practical. There are many languages that are Turing complete but ill suited for particular domain. It's been proven that SQL is Turing complete as well. However should you propose using SQL to write implementation of say FFT you are not likely to find much of a sympathy.

[ Parent | on HN ]
Re:Write code. Not too much. Mostly functions. by bob1029 on Tuesday December 22, 2020 @11:00AM (#25507582)
I would not use SQL to implement the actual algorithm, but I would certainly consider using it to hold all of the data around such an operation as required. For instance, tables like Samples, Spectrograms, etc.
[ Parent | on HN ]
Re:Write code. Not too much. Mostly functions. by trylist on Monday December 21, 2020 @10:44PM (#25502610)
Hierarchies are possible with an RDBMS, but I'd suggest it's the wrong tool to model them with, unless they're static of course. Really any graph that can't be encoded in the table relationships themselves.
[ Parent | on HN ]