"I have two tables, one is product which is a parent table with one primary key and I have another child table of product, which is a product_details table. But the child table is linking with parent table(product) with logical data instead of foreign key,as we are doing this relationship with the help of java code in the coding side, instead of depending on the data base, which make it as tight couple. To avoid tight coupling between the tables we are storing the primary key value in the child table.

CREATE TABLE `tbl_product` (
  `product_id` varchar(200) NOT NULL,
  `product_details_id` varchar(200) DEFAULT NULL,
  `currency` varchar(20) DEFAULT NULL,
  `lead_time` varchar(20) DEFAULT NULL,
  `brand_id` varchar(20) DEFAULT NULL,
  `manufacturer_id` varchar(150) DEFAULT NULL,
  `category_id` varchar(200) DEFAULT NULL,
  `units` varchar(20) DEFAULT NULL,
  `transit_time` varchar(20) DEFAULT NULL,
  `delivery_terms` varchar(20) DEFAULT NULL,
  `payment_terms` varchar(20) DEFAULT NULL,
  PRIMARY KEY (`product_id`));

CREATE TABLE `tbl_product_details` (
  `product_details_id` varchar(200) NOT NULL,
  `product_id` varchar(200) DEFAULT NULL,
  `product_name` varchar(50) DEFAULT NULL,
  `landingPageImage` varchar(100) DEFAULT NULL,
  `product_description_brief` text CHARACTER SET latin1,
  `product_description_short` text CHARACTER SET latin1,
  `product_price_range` varchar(50) DEFAULT NULL,
  `product_discount_price` varchar(20) DEFAULT NULL,
  `production_Type` varchar(20) DEFAULT NULL,
  PRIMARY KEY (`product_details_id`),
  UNIQUE KEY `product_id` (`product_id`));

Please suggest the Pros and Cons of the design, we are following this kind of relationship in my company, as the manager is saying it will give [us flexibility]. I know that if we lose the data from the table, we can't know the relationship between the two tables."--StackExchange.com

"I have two tables, one is product which is a parent table with one primary key and i do have another child table of product, which is a product_details table. But the child table is linking with parent table(product) with logical data instead of foreign key,as we are doing this relationship with the help of java code in the coding side, instead of depending on the data base, which make it as tight couple. To avoid tight coupling between the tables we are storing the primary key value in the child table.

CREATE TABLE `tbl_product` (
 `product_id` varchar(200) NOT NULL,
 `product_details_id` varchar(200) DEFAULT NULL,
 `currency` varchar(20) DEFAULT NULL,
 `lead_time` varchar(20) DEFAULT NULL,
 `brand_id` varchar(20) DEFAULT NULL,
 `manufacturer_id` varchar(150) DEFAULT NULL,
 `category_id` varchar(200) DEFAULT NULL,
 `units` varchar(20) DEFAULT NULL,
 `transit_time` varchar(20) DEFAULT NULL,
 `delivery_terms` varchar(20) DEFAULT NULL,
 `payment_terms` varchar(20) DEFAULT NULL,
 PRIMARY KEY (`product_id`));

CREATE TABLE `tbl_product_details` (
 `product_details_id` varchar(200) NOT NULL,
 `product_id` varchar(200) DEFAULT NULL,
 `product_name` varchar(50) DEFAULT NULL,
 `landingPageImage` varchar(100) DEFAULT NULL,
 `product_description_brief` text CHARACTER SET latin1,
 `product_description_short` text CHARACTER SET latin1,
 `product_price_range` varchar(50) DEFAULT NULL,
 `product_discount_price` varchar(20) DEFAULT NULL,
 `production_Type` varchar(20) DEFAULT NULL,
 PRIMARY KEY (`product_details_id`),
 UNIQUE KEY `product_id` (`product_id`));

Please suggest the Pros and Cons of the design, we are following this kind of relationship in my company, as the manager is saying it will give us flexible to us. I know that if we lose the data from the table, we can't know the relationship between the two tables."--StackExchange.com

"Nowadays, anyone who wishes to combat lies and ignorance and to write the truth must overcome at least five difficulties. He must have:

1. The keenness to recognize it, although it is everywhere concealed;
2. The courage to write the truth when truth is everywhere opposed;
3. The skill to manipulate it as a weapon;
4. The judgement to select in whose hands it will be effective, and
5. The cunning to spread the truth among such persons."

--Berthold Brecht

• Graph DBMSs;
• XML;
• JSON;
• NoSQL;
• Application-specific databases and DBMSs;
• "Unstructured data";
• No integrity enforcement;
• A cacophony of imperative programming languages rather than declarative data sublanguages (suffixed with QL, just like old non-relational DBMSs were with /R). 

Data Sublanguages, Programming and Data Integrity

• Review by Craig Mullins: A Useful Guide to Data Fundamentals from Fabian Pascal
• Review by Todd Everett.

"The value of the model may be diminishing in certain enterprises, since busy with deliverables." --Harshendu Desai, LinkedIn.com

5 Reasons Relational Databases Hold Back Your Business

• What a Database Really Is: Predicates and Propositions
• The Logical Fallacies

• If a table with a surrogate key has a column known to have unique non null values (eg SSN), does it violate 3NF
• Data Skeptic

And now for something completely different

• Ban: Security Council resolution on settlements showed ‘leadership’. This, from a man who, with a straight face, criticized Israel policies while admitting the UN is biased against Israel. The only leadership the UN has ever shown is in anti-semitism.
• Moral Incoherence at the UN Security Council. “At a time when the Security Council does nothing to stop the slaughter of half a million people in Syria, it disgracefully gangs up on the one true democracy in the Middle East, Israel and calls the Western Wall ‘occupied territory.’” 

• Pennsylvania Jewish family blamed as Xmas play cancelled
• Florida synagogue ramps up security after getting hate mail
• Website targets Jews in white supremacist’s hometown (do it to blacks and see what happens) 

• Prince Charles warns of echoes of 'dark days' before World War I. No royal deplored GB's denial of Nazi camp survivors entry in Israel, but Arab/Muslim immigrants, now he's full of compassion. 
• Some UK universities ‘too anti-Semitic for Jewish students’. But not too concerned about this. 
• Prague subway worker allegedly threatened to behead Jewish passenger
  

Israel and the Occupation Myth

The Red Disaster. The "life" in Romania during the 60s. The Jews did the worst due to deep anti-semitism. America paid Ceausescu to get us out, but neither she nor Europe wanted us. Had there been no Israel, we would have probably starved to death, not necessarily in a rotten jail. Nobody talks about us, or the hundreds of thousands of the Jewish refugees kicked out from the Arab countries, none of whom were murderous, but everybody is obsessed with the suffering of the Palestinians, who are genocidal.

Ahmad Tibi urges Israelis not to ‘live by the sword’. As if she is allowed to live without it.

Bard, M., MYTHS AND FACTS: A GUIDE TO THE ARAB-ISRAELI CONFLICT

• Data Sublanguage Part 1: Relational vs. Computational Completeness
• Data Sublanguage Part 2: Data Manipulation and Definition
• Data Sublanguage Part 3: DBMS Language
• Data Sublanguage Part 4: Conclusion