Re: New content type

--001a11c29d46cfd535050e663ba4
Content-Type: text/plain; charset=UTF-8

APIs are nice. Use them. They ease your life.

On 6 February 2015 at 08:58, Nicolas <[email protected]> wrote:

> 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 <[email protected]>:
>
>> 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 <[email protected]> wrote:
>>
>>
>> 2015-02-05 10:37 GMT+01:00 Muzaffer Tolga Ozses <[email protected]>:
>>
>>> 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.
>>
>>
>>
>


-- 
mto

--001a11c29d46cfd535050e663ba4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:courier =
new,monospace">APIs are nice. Use them. They ease your life.</div></div><di=
v class=3D"gmail_extra"><br><div class=3D"gmail_quote">On 6 February 2015 a=
t 08:58, Nicolas <span dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]=
" target=3D"_blank">[email protected]</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex"><div dir=3D"ltr">Thanks for your answer David. I unders=
tand that it&#39;s not as bad as I said. But when there&#39;s several hundr=
ed of queries per pages it can be runned on a dev environnement.</div><div =
class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><br><div clas=
s=3D"gmail_quote">2015-02-06 3:50 GMT+01:00 David Metzler <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:[email protected]" target=3D"_blank">metzler.dl@g=
mail.com</a>&gt;</span>:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"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 b=
y drupal.=C2=A0 I would not discard it out of hand just because you believe=
 it will take too many tables.=C2=A0 For example, it makes queries across c=
ontent types (e.g. calandars of multiple content types that have different =
numbers of fields in them) much more performative. =C2=A0=C2=A0</div><div><=
br></div><div>Shameless plug: If you&#39;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=3D"http://drupal.org/project/forena" targe=
t=3D"_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 &lt;<a href=3D"mailto:[email protected]" target=3D"_blank">nik=
[email protected]</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div>=
<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
2015-02-05 10:37 GMT+01:00 Muzaffer Tolga Ozses <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>&gt;</sp=
an>:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">If you don&#39;t want fields in your=
 content type, feel free to leave related parts out :) About entity, I don&=
#39;t know what you mean with that. Nodes are also entities.</blockquote><d=
iv><br></div><div>I know node are entities. I search for an article explain=
ing how to create a new content type (available from node/add/my-content-ty=
pe), using entities, without field api.=C2=A0</div></div><br><br></div></di=
v>
</div></blockquote></div></blockquote></div><br></div>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div class=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr">mto</=
div></div></div></div>
</div>

--001a11c29d46cfd535050e663ba4--