Understanding the drupal tables
I am reviewing a old system that another developer did with Drupal but i do not understand very well this problem:
There is a node table.
There is another table which it's field_data_field_worker.
field_data_field_worker has a entity_id which makes the relation between node table and field_data_field_worker, that's ok.
There is a node table.
There is another table which it's field_data_field_vacations
field_data_field_vacations has a entity_id which makes the relation between node table and field_data_field_vacations, that's ok.
The problem is that... how i can know this:
When i go to the worker detail, it shows the vacations belong to that worker... but how does Drupal make the relation between the worker and the vacation? because i just see that the unique relation it's node with worker and node with vacation but how Drupal realates worker with vacation? it's not with the node table because... the nodes belong to worker are not same nodes belong to vacation.
Thanks!!
drupal
add a comment |
I am reviewing a old system that another developer did with Drupal but i do not understand very well this problem:
There is a node table.
There is another table which it's field_data_field_worker.
field_data_field_worker has a entity_id which makes the relation between node table and field_data_field_worker, that's ok.
There is a node table.
There is another table which it's field_data_field_vacations
field_data_field_vacations has a entity_id which makes the relation between node table and field_data_field_vacations, that's ok.
The problem is that... how i can know this:
When i go to the worker detail, it shows the vacations belong to that worker... but how does Drupal make the relation between the worker and the vacation? because i just see that the unique relation it's node with worker and node with vacation but how Drupal realates worker with vacation? it's not with the node table because... the nodes belong to worker are not same nodes belong to vacation.
Thanks!!
drupal
add a comment |
I am reviewing a old system that another developer did with Drupal but i do not understand very well this problem:
There is a node table.
There is another table which it's field_data_field_worker.
field_data_field_worker has a entity_id which makes the relation between node table and field_data_field_worker, that's ok.
There is a node table.
There is another table which it's field_data_field_vacations
field_data_field_vacations has a entity_id which makes the relation between node table and field_data_field_vacations, that's ok.
The problem is that... how i can know this:
When i go to the worker detail, it shows the vacations belong to that worker... but how does Drupal make the relation between the worker and the vacation? because i just see that the unique relation it's node with worker and node with vacation but how Drupal realates worker with vacation? it's not with the node table because... the nodes belong to worker are not same nodes belong to vacation.
Thanks!!
drupal
I am reviewing a old system that another developer did with Drupal but i do not understand very well this problem:
There is a node table.
There is another table which it's field_data_field_worker.
field_data_field_worker has a entity_id which makes the relation between node table and field_data_field_worker, that's ok.
There is a node table.
There is another table which it's field_data_field_vacations
field_data_field_vacations has a entity_id which makes the relation between node table and field_data_field_vacations, that's ok.
The problem is that... how i can know this:
When i go to the worker detail, it shows the vacations belong to that worker... but how does Drupal make the relation between the worker and the vacation? because i just see that the unique relation it's node with worker and node with vacation but how Drupal realates worker with vacation? it's not with the node table because... the nodes belong to worker are not same nodes belong to vacation.
Thanks!!
drupal
drupal
asked Nov 22 '18 at 20:58
Jesus CovaJesus Cova
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Drupal's database structure is fairly complex so you should make custom queries only if you really need to do that. In all other cases do it "drupalish" way.
Use node_load()
function to get whole node object, node_save()
(or alternative for D8) to save the node.
For querying multiple nodes use views
module.
Point is - you don't have to understand Drupal's database structure - it's under the hood. Use the tools Drupal provides to work with database.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53437907%2funderstanding-the-drupal-tables%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Drupal's database structure is fairly complex so you should make custom queries only if you really need to do that. In all other cases do it "drupalish" way.
Use node_load()
function to get whole node object, node_save()
(or alternative for D8) to save the node.
For querying multiple nodes use views
module.
Point is - you don't have to understand Drupal's database structure - it's under the hood. Use the tools Drupal provides to work with database.
add a comment |
Drupal's database structure is fairly complex so you should make custom queries only if you really need to do that. In all other cases do it "drupalish" way.
Use node_load()
function to get whole node object, node_save()
(or alternative for D8) to save the node.
For querying multiple nodes use views
module.
Point is - you don't have to understand Drupal's database structure - it's under the hood. Use the tools Drupal provides to work with database.
add a comment |
Drupal's database structure is fairly complex so you should make custom queries only if you really need to do that. In all other cases do it "drupalish" way.
Use node_load()
function to get whole node object, node_save()
(or alternative for D8) to save the node.
For querying multiple nodes use views
module.
Point is - you don't have to understand Drupal's database structure - it's under the hood. Use the tools Drupal provides to work with database.
Drupal's database structure is fairly complex so you should make custom queries only if you really need to do that. In all other cases do it "drupalish" way.
Use node_load()
function to get whole node object, node_save()
(or alternative for D8) to save the node.
For querying multiple nodes use views
module.
Point is - you don't have to understand Drupal's database structure - it's under the hood. Use the tools Drupal provides to work with database.
answered Nov 23 '18 at 9:12
MilanGMilanG
4,87211936
4,87211936
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53437907%2funderstanding-the-drupal-tables%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown