Re: Some interesting criticisms of rails



2005/9/17, Robert Klemme <bob.news@xxxxxxx>:
>
> First of all it's five philosophers (i.e. as far as I remeber it's important
> that the number of resource aquisitors is odd).

http://en.wikipedia.org/wiki/Dining_philosophers_problem

Not only five philosophers, but five forks too.

The solutions here are very much about moving the complexity out of
the application and into the database, which is fine if your database
can handle it. It doesn't *remove* the complexity as such, it just
means that you can stop worrying about it until your database servers
die, which in your average web app probably won't happen.

Douglas


.



Relevant Pages

  • Re: OO vs. RDB challenge
    ... > complexity of mapping database tables to objects is useful only if the ... You would use the DBMS. ... > need to be thread safe because a thread can only get an instance of it ...
    (comp.object)
  • Re: OO vs. RDB challenge
    ... >>language, and especially with regards to distinguishing positional ... > complexity of mapping database tables to objects is useful only if the ... > public static bool IsUserInGroup(string user, string group) ...
    (comp.object)
  • Re: Commons pass ID Bill - police state circle nearly closed
    ... optimisation and perfromance of the database. ... non-functional complexity rather than functional complexity but then most ... the functionality it not so much the issue. ... ID cards database itself, but linking the ID card database to other ...
    (uk.legal)
  • Re: OO vs. RDB challenge
    ... >> policy is ensured by to be valid by the property set method. ... version might be okay in the simplest of requirements. ... are the one who was *insisting* on not adding unnecessary complexity, ... they are implemented in the database is because it is too inefficent to send ...
    (comp.object)
  • Re: Generating SQL
    ... >> IMHO it is well worth the time to create a data access layer to address ... > just add more complexity than it's worth. ... you would easily understand the database logic. ...
    (comp.object)