6784-delete-clientTypeFk #2059
No reviewers
Labels
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: verdnatura/salix#2059
Loading…
Reference in New Issue
No description provided.
Delete Branch "6784-delete-clientTypeFk"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@ -48,3 +48,3 @@
JOIN ticket t ON t.id = s.ticketFk
JOIN client c ON c.id = t.clientFk
JOIN clientType ct ON ct.id = c.clientTypeFk
JOIN clientType ct ON ct.code = c.typeFk
este join ja sobra
Sí, es cert, ho canvie en els 3 casos i ho tinc en compte per a canviar-ho en els 2 de access.
@ -45,3 +45,3 @@
JOIN ticket t ON t.id = s.ticketFk
JOIN client c on c.id = t.clientFk
JOIN clientType ct ON ct.id = c.clientTypeFk
JOIN clientType ct ON ct.code = c.typeFk
este join ja sobra
@ -48,3 +47,4 @@
JOIN clientType ct ON ct.code = c.typeFk
WHERE t.shipped BETWEEN util.VN_CURDATE() AND util.dayend(util.VN_CURDATE())
AND st.saleFk IS NULL
AND ct.code IN ('normal', 'trust')
c.typeFk , tant ací com en els altres llocs
@ -45,4 +44,0 @@
include: {
relation: 'type',
scope: {
fields: ['code', 'description']
atencio ací perque al ser back cap la posibilitat de que quan ho puges t'obriguen un cau de que algu accedia a sale y consultaba la propietat description..
Es de veres, ahí m'he vingut amunt, he retornat la relació i els 2 camps i ha passat el test correctament. Quan ho tinga tot t'ho puje.