Interfaces 103: Build Complex Interfaces by Adapting Patterns

RE: Interfaces 103: Build Complex Interfaces by Adapting Patterns

bhuvneshg0001 — Tue, 14 May 2024 14:16:30 GMT

Thanks .

RE: Interfaces 103: Build Complex Interfaces by Adapting Patterns

bhuvneshg0001 — Tue, 14 May 2024 14:16:07 GMT

Thanks .

RE: Interfaces 103: Build Complex Interfaces by Adapting Patterns

Shubham Aware — Tue, 14 May 2024 13:34:27 GMT

CREATE TABLE `PF_ACCOUNT` (
  `ACCOUNT_ID` int(11) NOT NULL AUTO_INCREMENT, 
  `TYPE_ID` int(11) DEFAULT NULL,
  `BALANCE` double DEFAULT NULL,
  `NAME` varchar(255) DEFAULT NULL,
  PRIMARY KEY (`ACCOUNT_ID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb3 COLLATE=utf8mb3_general_ci;

bhuvneshg0001 You can't create table without primary key.
I assumed that 'ACCOUNT_ID' will be a primary key.
A primary key is a crucial element in a relational database table, and MySQL requires it for InnoDB tables (the engine you're using).

RE: Interfaces 103: Build Complex Interfaces by Adapting Patterns

Karumuru Abhishek — Tue, 14 May 2024 13:33:51 GMT

hi bhuvneshg0001 database table must have a primary key for the Option to insert, update, restore, or delete data from a database table.

CREATE TABLE `PF_ACCOUNT` (
  `ACCOUNT_ID` int(11) NOT NULL,
  `TYPE_ID` int(11) DEFAULT NULL,
  `BALANCE` double DEFAULT NULL,
  `NAME` varchar(255) DEFAULT NULL,
  PRIMARY KEY (`ACCOUNT_ID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb3 COLLATE=utf8mb3_general_ci