Thanks for your answer David. I understand that it's not as bad as I said. But when there's several hundred of queries per pages it can be runned on a dev environnement.
2015-02-06 3:50 GMT+01:00 David Metzler <metzler...@gmail.com>: > As a database developer (oracle, Postgres, MySQL, mssql), I can say that > there are some distinct advantages to the entity value approach used by > drupal. I would not discard it out of hand just because you believe it > will take too many tables. For example, it makes queries across content > types (e.g. calandars of multiple content types that have different numbers > of fields in them) much more performative. > > Shameless plug: If you're a database developer and handy with SQL and are > planning on building your own custom tables/entities then you might > consider using http://drupal.org/project/forena > > Dave > > Sent from my iPad > > On Feb 5, 2015, at 1:39 AM, Nicolas <nikro...@gmail.com> wrote: > > > 2015-02-05 10:37 GMT+01:00 Muzaffer Tolga Ozses <to...@ozses.net>: > >> If you don't want fields in your content type, feel free to leave related >> parts out :) About entity, I don't know what you mean with that. Nodes are >> also entities. > > > I know node are entities. I search for an article explaining how to create > a new content type (available from node/add/my-content-type), using > entities, without field api. > > >
