In drupal should I use content-types or database abstraction layer?

Question

I posted a question on the drupal forum about whether I should build my database in drupal using content-types or the database abstraction layer and schema module: here

Any advice would be greatly appreciated.

Happy Christmas.

Answer 1

I'd recommend using content types.

For a PHP coder, sometimes using the Drupal User Interface to build things feels non-intuitive, but in the long run you're going to benefit a lot from doing things "the drupal way.

Once you reverse engineer your need into a content type and all it's associated fields, install the modules that provide those field types and set things up, you'll start to see the benefits.
* Validation on all the data-entry froms will already be done for you. * Multiple display modes are available for your data (email addresses can be shown with or without mailto: links, images can be shown using any of Drupal's image styles) * Integration with other Drupal modules already exists, and will be supported (almost anything built with fields is available to views)

By writing your own schema you'll need to handle all these things yourself (and more), and not just once, but you'll need to maintain all that custom code over time.

Learn to leverage the community and all the great work that's been done already, you'll save yourself time in the long run :)

Answer 2

What i see you are going to have shop site. You may tray this: https://drupal.org/project/commerce_kickstart

, i've found it usefull once. It's drupal distribution with nice themed shop rady to use straight forward.

And of course do it with content type + views + entity reference modules.

Answer 3

Here is a link to a comment that answers the question I asked. It backs up what arpitr outlined in their answer on the orignal post on the drupal forum, whose answer is also in agreement with jenlampton's suggestion above.

https://drupal.org/comment/7848011#comment-7848011

I will implement my system using node entities until the need arises to build a custom entity (if it ever does).

The top answer in this forum give a good way to evaluate whether to use nodes or custom build an entity:

https://drupal.stackexchange.com/questions/22586/when-is-it-appropriate-to-create-an-entity-versus-just-adding-a-new-content-type