Problem Description
I have SQLite database in which I have keep two tables, In first Table Companies I keep company ID which is unique for that company, Name of company, Websites and Emails. Every company can have several addresses, so I create second Table Addresses and keep there company ID which is not unique in this case and other information.
For Example:
If in Companies table I have record like this
7785413 MyComp http://www.mycomp.com mycomp#email.com
In the Addresses table I can have records like this
7785413 0 Address1 +64841518549 +9985212848
7785413 1 Address2 +64841542359 +9985212848
As there is no unique columns in my second Table, I want to know how I can update records?
In first case I call
database.insertOrThrow(DATABASE_TABLE_NAME, null, values);
function and if my IDs are same function throws an exception I catch it and update record. I can't do same thing in second Table as there is no unique columns and function will not throw an exception. Which is the best way to do that ?
Tables
CREATE TABLE Companies (ID TEXT UNIQUE, Name TEXT, Websites TEXT, Emails TEXT)
CREATE TABLE Addresses (ID TEXT, Position NUMERIC, Address TEXT, Tel TEXT, Mob TEXT)
You need to specify the primary key as a constraint on table creation.
CREATE TABLE Addresses(ID TEXT, Position NUMERIC, Address TEXT, Tel TEXT, Mob TEXT, PRIMARY KEY (ID , Position ));
Related
I have a question regarding the Cassandra data modelling while choosing the strategy.
I need to store the employee data that consists of attributes like id, name, email, date of birth, designation but these attributes will grow in future.
The partition key is going to be id.
There are two ways to design the table
Create employee table:
CREATE TABLE employee_horizontal (
id text,
name text,
email text,
dob DATE,
designation text,
PRIMARY KEY (id)
) ;
But here I have the limitation that I can query using id
Create employee table:
CREATE TABLE employee_kv (
id,
key text, (predefined set of attributes name, email,dob, designation)
value text,
PRIMARY KEY (id,key)
);
The above table will give leverage to do a lookup based on id and key (if that key exists for employees).
Could someone please suggest some pros/cons for the above strategy?
Cassandra modeling advocates denormalization of data. Also modeling principle of Cassandra says design your tables based on your queries. So write down your queries first. For example if your queries could be like:
Get employee by Id.
Get employee by email Id.
Get employee by designation.
Now to create a data model for your query, you have to create following tables
For Query 1,
CREATE TABLE employee_by_id (
id text,
name text,
email text,
dob DATE,
designation text,
PRIMARY KEY (id)) ;
For Query 2,
CREATE TABLE employee_by_email (
id text,
name text,
email text,
dob DATE,
designation text,
PRIMARY KEY (email)) ;
For Query 3,
CREATE TABLE employee_by_designation (
id text,
name text,
email text,
dob DATE,
designation text,
PRIMARY KEY ((designation), name)) ;
This is just an example to show how to model your data for Cassandra. You cannot have a single table responding all your queries.
I'm very new to SQL and I want the contracts_tb (query details below) is to display and link the foreign id keys referred from:
med_idref (referred from med_id (INTEGER), PRIMARY KEY o mediaadv_tb),
mediatitle_ref (title (TEXT), mediaadv_tb),
mediatype_red (mtype (TEXT), mediaadv_tb),
cus_idref (cus_id (INTEGER),PRIMARY KEY of customer_tb),
cus_companyref (referred from company (TEXT), in customer_tb)
All to be linked and displayed to contracts_tb. When I add/replace values from mediaadv_tb and customer_tb, I get this problem:
foreignkey mismatch
Also, do I have to make or assign a parent table?
Query:
DROP TABLE IF EXISTS customer_tb;
CREATE TABLE IF NOT EXISTS customer_tb (
cus_id INTEGER PRIMARY KEY,
company TEXT,
firstname TEXT,
middlename TEXT,
lastname TEXT,
gender TEXT,
dob TEXT,
dateregistered TEXT,
contactno TEXT,
emailaddress TEXT,
description TEXT,
refpic INTEGER,
cuspic BLOB
);
DROP TABLE IF EXISTS mediaadv_tb;
CREATE TABLE IF NOT EXISTS mediaadv_tb (
med_id INTEGER PRIMARY KEY,
mtype TEXT,
duration TEXT,
title TEXT,
dateadded TEXT,
desription TEXT,
previewimg BLOB,
filepath TEXT
);
DROP TABLE IF EXISTS contracts_tb;
CREATE TABLE IF NOT EXISTS contracts_tb (
contract_id INTEGER PRIMARY KEY,
customer_idref INTEGER REFERENCES customer_tb (cus_id),
media_idref INTEGER REFERENCES mediaadv_tb (med_id),
media_typeref TEXT REFERENCES mediaadv_tb(mtype),
media_titleref TEXT REFERENCES mediaadv_tb (title),
status TEXT,
priority TEXT,
dateadded TEXT,
dateexpiration TEXT,
amountpaid REAL,
arearofcoverage TEXT
);
Error :-
contracts_tb
mediaadv_tb
I believe that your issue is because the foreign keys defined that reference the media_typeref and the media_titleref columns are invalid as they do not have, or are part of a, UNIQUE indexes (no indexes). SQLite Foreign Key Support - 3. Required and Suggested Database Indexes
The referenced id columns, as they are INTEGER PRIMARY KEY, are implicitly UNIQUE indexes.
Furthermore the two columns (typeref and titleref) themself aren't even needed as the media_idref column would be used to identify the reference and thus would hold the respective values. Copying those values into the contracts table would be contrary to normalisation and may even create major headaches (e.g. if a value changed you'd have to find all other uses and also change them).
As such I'd suggest that the contracts_tb be created using :-
DROP TABLE IF EXISTS contracts_tb;
CREATE TABLE IF NOT EXISTS contracts_tb (
contract_id INTEGER PRIMARY KEY,
customer_idref INTEGER REFERENCES customer_tb (cus_id),
media_idref INTEGER REFERENCES mediaadv_tb (med_id),
status TEXT,
priority TEXT,
dateadded TEXT,
dateexpiration TEXT,
amountpaid REAL,
arearofcoverage TEXT
);
Re comment :-
What i'm making is a Java NetBeans SQLite database program, where by
using the Contracts frame, whevenr one makes a new contract, there
will be a combobox that restricts the user to only put the existing
ids or names that is referred in the contracts_tb then provides the
choices. Is it possible sir?
Yes.
More specifically:-
Assume that you have customers Fred, Bert and Harry (id's 1,2 and 3 respectively). And that you have mediaadv's M1, M2 and M3 (id's 10,11 and 12 (not 1,2 and 3 to help distinguish between mediaadv and customers)).
Additionally I'll assume the suggested contracts_tb table as opposed to the original in the question (i.e. 2 columns dropped as suggested)
The when inserting a new contract, you present a list (combobox) of the customers e.g.
Fred
Bert
Harry
(this list could be generated from a query such as:-
SELECT cus_id,firstname FROM customer_tb; i.e. all existing customers)
If you wanted Fred James Bloggs then you could use :-
SELECT cus_id,firstname||' '||middlename||'lastname' AS fullname FROM customer_tb;.
Likewise a list of the existing mediaadv could be generated from a query such as:-
SELECT med_id, description FROM mediaadv_tb; e.g.
so the combobox would have:-
M1
M2
M3
Now if the contract were for Bert (id 2) and M1 (id 10) then you build SQL something like :-
INSERT INTO contracts_tb VALUES(null,2,10,'the_status','the_priority','yyyy-mm-dd','yyyy-mm-dd',500,'the_coverage');
1st value is null i.e. no value, so as contract_id is an alias of the rowid it will be generated.
2 is the id of the customer (hence why cus_id was in the query as you need the id as it's the value you are going to store)
10 is the id of the mediaadv (again hence why med_id was in the query as you need the id as it's the value you are going to store).
the other values are what they should be.
Note the above use of INSERT requires that all columns be given. You can skip columns by specifying a list of the columns e.g. INSERT INTO contracts_tb (customer_idref,media_idref) VALUES(2,10);
As a customer with an cus_id of 2 (Bert) exists then the constraint that customer_idref is an existing id in the customer_tb is good/met and there is no conflict.
Likewise as there is a row in mediaadv_tb that has an med_id of 10 this constraint is good/met and there is no conflict.
However say the SQL were :-
INSERT INTO contracts_tb VALUES(null,2,100,'the_status','the_priority','yyyy-mm-dd','yyyy-mm-dd',500,'the_coverage');
Then as there is no med_id of 100 the constraint saying that media_idref must reference a value of 100 (in this instance) in the mediaadv_tb, column med_id, then the constraint will not be met and the insert will fail.
So again Yes, I believe that what you want is feasible.
Note a foreign key is only a constraint it doesn't bind/associate columns or join tables.
I'm working on my first db and executing statements through java. I have 2 columns in the db named
Playername
PlayerType
I need to update the row if my query corresponds to these 2 columns.
So there can be multiple player names and multiple player types but never more than 1 exact player type and exact player name.
If the row doesn't exist create a new one. What's the best way to go about this?
You first have to set a multiple field primary key
CREATE TABLE Players
(
PlayerName varchar(16) NOT NULL, //Not null not required as it is part of pk but more readable
PlayerType varchar(16) NOT NULL,
//Other fields
CONSTRAINT pk_PlayersID PRIMARY KEY (PlayerName ,PlayerType )
)
And then you use
INSERT INTO Players(PlayerName , PlayerType ,....) VALUES(PN, PT, ....) ON DUPLICATE KEY UPDATE
PlayerName VALUES(PlayerName ), PlayerType =VALUES(PlayerType ),...
I was given two databases, and am supposed to create a table in a new database that stores information about the given databases.
So far I created a table in a new database. I also defined its attributes, but I am stuck on how to populate this table.
The attributes are things like 'original_db, 'original_field' etc , but I don't know how to access this information? Especially since I would need to connect jdbc to 3 databases (the new one, and the 2 old ones) at the same time. Is ths even possible?
I am new to working on databases and SQLite, so sorry if this is a stupid problem.
I would be so grateful for any advice!
What I can grasp from your question is you don't know how to insert data into it?
You could do this in your schema.sql when creating the db e.g the schema would look something like.
DROP TABLE users;
CREATE TABLE users(id integer primary key, username varchar(30), password varchar(30), email varchar(50), receive_email blob, gender varchar(6));
DROP TABLE lists;
CREATE TABLE lists(id integer primary key, user_id integer, list_id integer, name varchar(50), creation_date datetime, importance integer, completed blob);
DROP TABLE list_item;
CREATE TABLE list_item(id integer primary key, list_id integer, name varchar(50), creation_date datetime, completed blob);
then you could make a data.sql file or something with
INESRT into users VALUES(NULL, "name", ...);
and then do in the terminal
sqlite3 database.db <- data.sql
or you could start a sqlite interactive session in the same working directory as your db and manually type in the code
e.g type in
sqlite3 databasename.db
and then type in commands from there
i have 2 table
1 persons(email,name)
2 location(email)
now when i add a person to persons table i want the db auto creat a row in location whit the person email (that i just add to persons).
i try to do it white PRIMARY KEY, and FOREIGN KEY but no succses.
thank you all.
this what i try :
CREATE TABLE Persons
(
Email char(50) PRIMARY KEY,
First_Name char(50))
CREATE TABLE location
(
email char(50),
FOREIGN KEY (email) REFERENCES Persons(email)
)
but when i add to persons person its not added to location too.
You would need a trigger to do this not a foreign key.
The FK just enforces that a row cannot be inserted in location without a corresponding record in Persons
But email is a very wide choice for a primary key as well as unstable (see is email address a bad primary key) and the whole design seems odd.
What is the location table for? Does this have a 1:many relationship with Persons? Where are the other columns? What is the PK of location?