| bio | website | phpfreaks.com |
|---|---|---|
| location | United States (but travelling) | |
| age | 33 | |
| visits | member for | 1 year, 7 months |
| seen | 2 days ago | |
| stats | profile views | 31 |
I am not a handy programmer but I play with php with a hope to develop creative ideas.
|
Feb 29 |
asked | How to use RESTRICT for Foreign Key in mysql? |
|
Feb 29 |
comment |
Two-sided UNIQUE INDEX for two columns very interesting approach to solve the problem! Though I am not generally a fond of triggers; but it seems sometimes they are necessary ;) |
|
Feb 29 |
comment |
Two-sided UNIQUE INDEX for two columns @DaveMarkle You have a great nose ;) This is actually a normalized database of many-to-many relationship and this table is the map between two main tables. |
|
Feb 29 |
comment |
Two-sided UNIQUE INDEX for two columns This is the reason that I asked this question. I am looking for a trick to avoid 54,33 too; as UNIQUE INDEX cannot do this. |
|
Feb 29 |
comment |
Two-sided UNIQUE INDEX for two columns What you are referring to is about UNIQUE INDEX separately for each column. UNIQUE INDEX (col1, col2) make the combination unique. |
|
Feb 29 |
asked | Two-sided UNIQUE INDEX for two columns |
|
Feb 29 |
comment |
Usefulness of Foreign Key WITHOUT reference option Very helpful answer. But I believe ON DELETE is quite useful. For example, when deleting a post, comments are not necessary and should be deleted to. Here in stackexchange, when deleting a Questions, Answers should be deleted by ON DELETE. |
|
Feb 29 |
asked | Usefulness of Foreign Key WITHOUT reference option |
|
Feb 28 |
comment |
Using Foreign Key and References for ON DELETE CASCADE in mysql vivid clarification of the issue! Thanks :) |
|
Feb 28 |
awarded | Editor |
|
Feb 28 |
comment |
Using Foreign Key and References for ON DELETE CASCADE in mysql The missing type was typo in writing here. The types are all the same in parent, child1, and child2. Yes, I also think that I must use the secure syntax of child2; but still curious to know what the first one does not work ;) |
|
Feb 28 |
revised |
Using Foreign Key and References for ON DELETE CASCADE in mysql added 8 characters in body |
|
Feb 28 |
accepted | Usage of RESTRICT or No ACTION in FOREIGN KEY Constraints |
|
Feb 28 |
asked | Using Foreign Key and References for ON DELETE CASCADE in mysql |
|
Feb 21 |
awarded | Supporter |
|
Feb 21 |
comment |
Usage of RESTRICT or No ACTION in FOREIGN KEY Constraints Some points are vague to me: 1. You mean that whether using RESTRICT or omitting it in column1 is the same? then this is optional? 2. You talked about orphan children. In the present case, there should be NO orphan, as ON DELETE CASCADE should guarantee deleting the child upon deleting the parent. Am I right? |
|
Feb 21 |
asked | Usage of RESTRICT or No ACTION in FOREIGN KEY Constraints |
|
Oct 14 |
awarded | Student |
|
Oct 14 |
awarded | Scholar |
|
Oct 14 |
accepted | How SQLite index ID (or line number) |