0

How would you think if a designer extends the database of Drupal for a desired system? (for example adding field to some tables)

Would it be really PRACTICAL?

4
  • I mean that I'm going to do it! I need to hear your recommendation!
    – Ehsan
    Aug 11 '14 at 11:03
  • It is not recommended to change the existing database schema of Drupal, unless that is the only option left; which is most of the times is not the case. It might cause problems with the updates.
    – AjitS
    Aug 11 '14 at 11:08
  • Can you define what you mean by "practical" in this context? It's not really possible to answer this without knowing exactly what you want to change. Knowing why would also be helpful, so we can convince you to do it the proper way instead
    – Clive
    Aug 11 '14 at 11:12
  • I would like to add some fields to user table.
    – Ehsan
    Aug 11 '14 at 11:13
2

Bottom line: it's your database, you can add as many fields to whatever tables you like.

Drupal won't know anything about them, obviously, and it may cause unforeseen issues further down the line, as you're potentially changing the way the core system works. It's not possible to be any more specific than that without knowing pretty much everything about your application, so you'd need to test until you're happy you haven't broken anything.

The correct way to extend core entities is through the use of fields, I'd strongly recommend using those rather than hacking at database tables.

1
  • I tried to find the way with fields and it really worked. thanks
    – Ehsan
    Aug 11 '14 at 11:48

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.