<div dir="ltr"><div class="gmail_default" style="font-family:courier new,monospace">APIs are nice. Use them. They ease your life.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 6 February 2015 at 08:58, Nicolas <span dir="ltr"><<a href="mailto:nikrou77@gmail.com" target="_blank">nikrou77@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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.</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">2015-02-06 3:50 GMT+01:00 David Metzler <span dir="ltr"><<a href="mailto:metzler.dl@gmail.com" target="_blank">metzler.dl@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>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. </div><div><br></div><div>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 <a href="http://drupal.org/project/forena" target="_blank">http://drupal.org/project/forena</a></div><div><br></div><div>Dave</div><div><br>Sent from my iPad</div><div><br>On Feb 5, 2015, at 1:39 AM, Nicolas <<a href="mailto:nikrou77@gmail.com" target="_blank">nikrou77@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">2015-02-05 10:37 GMT+01:00 Muzaffer Tolga Ozses <span dir="ltr"><<a href="mailto:tolga@ozses.net" target="_blank">tolga@ozses.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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.</blockquote><div><br></div><div>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. </div></div><br><br></div></div>
</div></blockquote></div></blockquote></div><br></div>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">mto</div></div></div></div>
</div>