Primary key question with PHPmysql database

I know that updating the primary key is taboo, but I have a a newsletter subscription form set up that works perfectly, but I can't figure out how to create the primary key. I tried using the subscriber email address (because its unique, but in trying to add an update function I realize that the email address may need to be updated.
My question is how do I get a primary key that will work when I'm relying on a form variable to create the record and therefore have no control over assigning one?
Is there a way to have one automatically assigned when a subscriber hits the submit button?

Bingo.
I wrote:
ALTER TABLE email_list ADD ( id MEDIUMINT NOT NULL AUTO_INCREMENT, name CHAR(30) NOT NULL, PRIMARY KEY (id) )
I got my primary key column. thank you so much!!!

Similar Messages

Composite Primary key & Primary key questions

Background:
1.5 TB data warehouse. All tables use at least a 3 column composite Primary key. Most use 3. col1||col2||col3 to achieve uniqueness.
col1= very low cardinality. 99% of the values are '0'
col2 = high cardinality. (SSN's, loaded monthly)
col3 = low cardinality. (monthly sequence number used for partitioning)
From what I've read, the first column used in a composite primary key also receives its own index. If that is correct, then the primary key being used is losing its effectiveness by putting a very low cardinality column as the first column of the Primary key. By moving col2 to the first position of the composite key, I would be obtaining an index on SSN which would be much more useful. (Please correct me if I'm wrong) Or since the index would be so large anyway, the CBO would just do full table scans which is what I'm trying to get away from.
This Primary key is used to ensure uniqueness during loads. Other than that, it really has no purpose and is never queried by the user. (WHERE col1||col2||col3 = xxxxxxxxx)
As a DBA, I see this massive tablespace for holding the primary keys now reaching in excess of 157 GB and it seems like such a waste of space. The problem I'm running across is how to ensure uniqueness during the loads w/o having to store the unique values. (the 157 GB) If I drop the PK's, then create unique indexes just for the loads, then the unique index would be generated against the entire table, which would take forever.
If you create a local index (what I want in the end) it still has to create the index for all previous partitions (250+ partitions). You can't create a specific 'local' index on a partition. You create a local index on the table and when a new partition is added, the index is then added as well. That's what I want to do with some of my fields like SSN but for loading purposes, this isn't going to help me.
I need a way to ensure uniqueness during a monthly load of a new partition (col1||col2||col3) but w/o having to store these values for eternity. Right now it's the primary key, so it has to be stored. I hope I'm making sense here. Any ideas?

I think you need some clarification about the index supporting the primary key.
The primary key is unique - the database will enforce this for you.
All of the columns in the primary key are in the index that enforces the key (not just the first column).
Usually this index is a unique index, but you can have a non-unique index supporting a primary key.
I'm a little confused with some of your other statements
how to ensure uniqueness during the loads w/o having to store the unique valuesIf you don't store the value how do you know it is unique?
Did you mean that you don't want to store the key values in both the table and the index?
You may want to consider making col3 (the partition key) the leading column of the index, so you can create a local (instead of global) PK index.
I wouldn't worry too much about col1 (the column full of mostly zeros) - numbers are stored variable length. A NUMBER(38) that holds a zero takes no more space than a NUMBER(1) that holds a zero.

Database Primary Key Question - Best Practices

I posted this in the ADDT forum, but I imagine I'll get more
responses here:
All you database developers - how do you deal with primary
keys? Do you
ALWAYS use an AutoIncrement/AutoNumber? Or only sometimes? Is
there an
argument to NOT use AutoIncrement? I know how I create
databases and how
I usually do things. I know how a few of my colleagues work.
But how
about the rest of the world? (Research for a MS Access book I
am
involved with.)
Alec
Adobe Community Expert

.oO(Alec)
>I posted this in the ADDT forum, but I imagine I'll get
more responses here:
>All you database developers - how do you deal with
primary keys? Do you
>ALWAYS use an AutoIncrement/AutoNumber?
No.
>Or only sometimes? Is there an
>argument to NOT use AutoIncrement?
AUTO_INCREMENT is a proprietary MySQL feature. For some
people this
might be an argument against it, but doesn't have to. Every
DBMS has its
own special features. You just have to decide whether you
want to keep
your code/queries as portable as possible or want to get the
most out of
your DB. Usually I prefer performance/features over
portability, simply
because for me and my projects it's very unlikely that I have
to change
the DBMS. I've chosen MySQL for good reasons and will stay
with it for
quite a while.
>I know how I create databases and how
>I usually do things. I know how a few of my colleagues
work. But how
>about the rest of the world? (Research for a MS Access
book I am
>involved with.)
It always depends on the table itself, what data it contains,
what I
want to do with it and also some personal preferences. In n:m
tables for
example there's no need for an extra numeric PK, since the
entire record
already is the PK, built from two or more FKs.
But if I need a numeric PK, I usually use sequences. Some
DBMS support
them natively, in MySQL they can be emulated with an extra
table. It
simply means, that the used PK number is generated _before_
the record
itself is inserted. For me and my framework this has some
advantages
(makes the internal work a bit easier), but of course in
other cases an
AUTO_INCREMENT might be more appropriate.
So IMHO there's no general solution. If an AUTO_INCREMENT or
something
similar fits your needs, you should use it. I don't see a
real problem
with that.
Micha

ADF BC Primary key generation with SQL Server DB

Hi,
I am using ADF 11.1.1.6 to develop a small application that will do some very basic CRUD operations on a SQL Server DB.
I read through http://www.oracle.com/technetwork/developer-tools/jdev/multidatabaseapp-085183.html before I'm starting to implement the Entity objects.
This document describes a way to do primary key generation using a table created in the DB and instructs to create an application connection to the Database :
+2. Create a Connection to the Table+
In your application, create a database connection named ROWIDAM_DB that points to the database containing your S_ROW_ID table. Alternatively, edit your BC project's properties and add the following Java option to the project's run configuration:
-Djbo.rowid_am_conn_name= appconnection
where appconnection is the name of a database connection that points to the S_ROW_ID table.
My question is how do we do this when we mve to a production environment ?
Also I'll be interested to hear if anyone has any pointers for developing ADF apps with SQL Server. (gotchas, performance pitfalls etc. )
-Jeevan
Upadte : This is SQL Server 2005
Edited by: Jeevan Joseph on May 2, 2012 9:04 AM

my apologies to everyone ... This should have been very simple. I just need to provide the config in my AM configuration(bc4j.xml)
jbo.rowid_am_conn_name* should be set to the connection name you create. For production deployments, theres a similar
jbo.rowid_am_datasource_name* that should work just fine (though I havent tried if it has any hiccups).
I'd like to point out one thing though, for whoever might stumble upon this thread and find it useful later on...
After I did the steps above, everything seemed to work when I tested the app from the AM tester. But when I built a UI for it in ADF Faces, I started getting an exception on Create/CreateInsert :
java.lang.ClassCastException: com.microsoft.sqlserver.jdbc.SQLServerConnection cannot be cast to oracle.jdbc.OracleConnection
     at oracle.jbo.server.OracleSQLBuilderImpl.setSessionTimeZone(OracleSQLBuilderImpl.java:5533)
     at oracle.jbo.server.DBTransactionImpl.refreshConnectionMetadata(DBTransactionImpl.java:5311)
     at oracle.jbo.server.DBTransactionImpl.initTransaction(DBTransactionImpl.java:1194)
     at oracle.jbo.server.DBTransactionImpl.initTxn(DBTransactionImpl.java:6826)
     at oracle.jbo.server.DBTransactionImpl2.connect(DBTransactionImpl2.java:136)
     at oracle.jbo.common.ampool.DefaultConnectionStrategy.connect(DefaultConnectionStrategy.java:213)The trouble is that the ADF Faces adf-config.xml overrides the AM configuration. Oracle is the default, and it overrides the SQL flavor I set when initializing the Model project.
This was not mentioned in the original document probably because ADF faces was out of scope for that document.
I also found this thread extremely useful, and its what reminded me of the ADF Faces AM config overrides : Re: Locking mode 'optupdate' with SQL92
Cheers !
Jeevan

ESB DbAdapter primary key question

Hi,
I have an ESB process that pushes data from a legacy table into the GL_INTERFACE table in Oracle E-Business Suite.
The DbAdapter for reading from the legacy table had two primary keys defined. We've recently learned that these two fields do not always uniquely identify a record. If I had two records with the same data in these two fields, they would both be inserted into the destination table, but the data inserted for both records would be the same as that of the first record (seemingly ignoring the second record). I solved this problem by defining a third primary key relationship in the DbAdapter, and that worked fine.
My question is this: why did both records inserted into the destination table contain the same data?
Any ideas?
Thanks in advance.

The the table in the database doesn't have a primary key defined, but, of course, Oracle's DBAdapter requries primary keys defined. There were actually two records in the database, with the same information in the columns that I defined as primary keys, but other information was different for the two records. It seems as though the ESB used the data from the first record when it encountered the second. Am I correct that this is what happened?

Identity without Primary Key or with....which is the difference

Guys, one question: which is the main difference between using Identity and using either Identity and Primary_Key? It looks a stupid question (and maybe it is) but...maybe is not so stupid.

Primary Key is a logical implemention which creates behind the scene unique clustered index (physical implementation)
BTW, if you use an INDENTITY property and do not have PK on this you may end up with duplicates , ans also someone my reseed the values...
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence
Using identity you may end up with duplicates??!!

Default Primary Key Field of any database table

hi,
I am working on a database in which the data in the tables is generated from some other modules. I have to add, view and update functionalities to this table in the database. Unfortunately there is no primary key field for the table i am working on and as some existing modules are using this table i am not allowed to change the design of the table at this stage.
Without primary i think its not possible to do updates. Because if all fields can have their values changed, then there will be a breakdown if the field value changes in the mid time when i had already retrieved the data to show on the screen, but not yet updated the value in the database. I hope you understood my problem.
Please suggest solutions. I am not sure, but i think i read somewhere that every table created has a default primary associated whose value is always incresing with a new addtion of recored and its value never decreases. But i am unable to recollect the field name...i think it is some thing like[b] OID .... But i checked there is no such field name by OID. So please help me with some alternative solution...or by telling the default primary key field name.
Thanx

All the databases I know (namely Informix, PostgreSQL, SQL Server, even Access) have a row id column generated automatically.
PostgreSQL example
There is a way to read the value of this column; for example with PostgreSQL let�s say you have the following:
CREATE TABLE no_id_column (
column_one varchar(80),
column_two varchar(80)
INSERT INTO no_id_column(column_one, column_two) VALUES (�red�, �pink�);
INSERT INTO no_id_column(column_one, column_two) VALUES (�yellow�, �orange�);Certainly, if we executed:
SELECT * FROM no_id_column;Would obtain:
column_one          column_two
red               pink
yellow               orangeBut if we modify the query
SELECT oid, * FROM no_id_column;We magically obtain a row identificator
oid          column_one          column_two
21569          red               pink
21570          yellow               orangeThe data in the oid column is generated automatically by the database manager. Every time we insert a row we�ll have a different one. Just take into account that if the database contains a large amount of data, the oid could cycle.

Primary key issue with adf Entry Form.

Hi All,
i'm using jdev version 11.1.1.5.0
use case: i have create simple entry form based on Eo and Vo using database table like student(enrollment no,name address)
where enrollment no is primary key.
so when i have create a record i have set enrollment no in entity impl class of this eo create method using some logic based on my need like(20130001)
for that i have read highest no from database field and assign to enrollment no field when user create record.
so when user create record second time then enrollment no is 20130002. and other detail like name and address user fill and commit record. and it is fine.
but problem is that when two user access same form at a time and create record so both have get same primary key like 20130003 because in current time in database maximum value is 20130002.
so which user commit record first it record will save on database and second user get error message because of primary key violation.
so my question is that where we generate primary key value for record so when multiple user access form have get different primary key value. and in my use case i can't use sequence and any autoincrement no
because i have patter for primary key.
Thanks in Advance
Manish

Hi,
Dimitar and Frank
thank for reply.
How can i apply non-concurrent DB lock can you please explain.(because lock method on entity impl not work when user create new row as per documentation)
http://docs.oracle.com/cd/B14099_19/web.1012/b14022/oracle/jbo/server/EntityImpl.html#lock__
i have write following line of code in entity impl class to set primary key value(reqid)-
    @Override
    protected void prepareForDML(int i, TransactionEvent transactionEvent) {
         super.prepareForDML(i, transactionEvent);
        this.setReqid(genReqid());
    public String genReqid() {
        String reqby = this.getReqby();
        String qry =
            "SELECT nvl(MAX(TO_NUMBER(SUBSTR(REQID,7))),0)+1 FROM STM_REQHDR WHERE REQBY=? AND REQTYPE<>'M' and substr(reqid,1,2)<>'MT' AND SUBSTR(REQID,1,3)<>'PAY'";
        PreparedStatement ps = null;
        String no = "";
        try {
            ps = getDBTransaction().createPreparedStatement(qry, 0);
            ps.setString(1, reqby);
            ResultSet rs = ps.executeQuery();
            if (rs.next()) {
                no = rs.getString(1);
            ps.close();
        } catch (Exception e) {
            System.out.println("Exception in Gen req id ==>" + e);
        String reqno = reqby + String.format("%6s", no).replace(' ', '0');
        return reqno;
but when i run form in debug mode and two user commit concurrent manner only one time code block is executed who first commit. and second user got error message.
thanks
Manish

Unable to enforce Primary Key constraint with my code

Hi Guys
I have a table that contains 2 columns: code and description (defined as not null). I am using oracle forms 10g, if I inset a new row both the columns: code and description should have data e.g. code: 001 and description: Main Store...
So on forms I have an on-update trigger on block level that handles the error messages but if the user has to update the description this trigger blocks him because the value for the code i.e. 001 is already on the database but if I remove the piece of code (the first IF block on my code together with a cursor and the entire declaration section)then the primary key constraint is violated: the code is as follows:
declare
v_store_code store_types.code%type;
cursor store_codes is
select a.code
from store_types a
where a.code = :b1.code;
begin
open store_codes;
fetch store_codes into v_store_code;
if ( store_codes%found ) then
Message('The Store Code you have entered already exists on the Store_Types table, please enter another code!');
Message('The Store Code you have entered already exists on the Store_Types table, please enter another code!');
close store_codes;
raise form_trigger_failure;
end if;
close store_codes;
if :b1.code is not null and :b1.description is null then
     message('If the Store Code has been captured, then the Store Description must be captured!');
     message('If the Store Code has been captured, then the Store Description must be captured!');
raise form_trigger_failure;
end if;
if :b1.description is not null and :b1.code is null then
     message('If the Store Description has been captured, then the Store code must be captured!');
     message('If the Store Description has been captured, then the Store code must be captured!');
     raise form_trigger_failure;
end if;
exception
          when others then
               message(sqlerrm);
               raise form_trigger_failure;
end;
My main intention here is: the user should be able to update the description field and save the changes without violating primary key on the column: code ...... please help me guys...

ICM
Sir as far I could understand , your problem is that your wanna allow the end users to update the Store_description , and Store_code..
So on forms I have an on-update trigger on block level that handles the error messages but if the user has to update the description this trigger blocks him because the value for the code i.e. 001 is already on the databaseif it's right then why don't you have unique key constraints Store_description?
alter the tables and apply unique key constraint...
and no need to write this code
f :b1.code is not null and :b1.description is null then
message('If the Store Code has been captured, then the Store Description must be captured!');
message('If the Store Code has been captured, then the Store Description must be captured!');
raise form_trigger_failure;
end if;because as you mentioned
code and description (defined as not null)if they are already under not null constraints then no need to handle this in coding..
he/she must be able to change the description and save the changes without affecting the code i.e.:Sir I think updation in records can only be performed when the forms is in query mode e.g execute query, have all/desired records and then make changes
(1)description is in unique key constraint it can't be duplicated ..
(2)code is PK it can never be duplicated...
for this I would suggest you to have a update button on forms , when-button-pressed trigger sets property of block (update_allowed, property_true);
and check the code of unique key violation code from oracle form's help , when that error code raise up you can show those message
Message('The Store Code you have entered already exists on the Store_Types table, please enter another code!');
Message('The Store Code you have entered already exists on the Store_Types table, please enter another code!');I hope it could do something for you
thanks
regards:
usman noshahi

Composite Primary Key question

I have a new question regarding composite primary keys on another table I have created.
I have the following table with the following definition:
CREATE TABLE "APSOM"."CPULIST"
( "CPU_ID" VARCHAR2(10 BYTE),
"SERVER_ID" VARCHAR2(10 BYTE),
"CREATED_DATETIME" TIMESTAMP (6),
"UPDATED_DATETIME" TIMESTAMP (6)
with the following composite PK definition:
ALTER TABLE "APSOM"."CPULIST" ADD CONSTRAINT "CPULIST_PK" PRIMARY KEY ("CPU_ID", "SERVER_ID")
Then, I inserted data in the following way:
insert into CPULIST
values ('CPU1', 'P1', SYSDATE, SYSDATE);
with following CPU ID values from 'CPU1' to 'CPU16' for SERVER ID value 'P1' also inserted as well.
Now, I am trying to insert values for SERVER ID value 'P2'
insert into CPULIST
values ('CPU1', 'P2', SYSDATE, SYSDATE);
and I am getting the following error message:
Error starting at line 1 in command:
insert into CPULIST
values ('CPU1', 'P2', SYSDATE, SYSDATE)
Error report:
SQL Error: ORA-00001: unique constraint (APSOM.XPKCPULIST) violated
00001. 00000 - "unique constraint (%s.%s) violated"
*Cause: An UPDATE or INSERT statement attempted to insert a duplicate key.
For Trusted Oracle configured in DBMS MAC mode, you may see
this message if a duplicate entry exists at a different level.
*Action: Either remove the unique restriction or do not insert the key.
Using the following SQL command:
select column_name from all_cons_columns
where constraint_name = 'CPULIST_PK'
and owner = 'APSOM';
I get the following records
1. CPU_ID
2. SERVER_ID
This error does not make sense to me. Any help would be appreciated.
Thanks,
Patrick Quinn
Operations
Turning Point Global Solutions

So, if there is a hidden unique constraint XPKCPULIST that cannot be pulled the all_cons_column table and I drop the XPXCPULIST constraint with the following SQL:
alter table CPULIST drop constraint XPKCPULIST;
Error starting at line 1 in command:
alter table CPULIST drop constraint XPKCPULIST
Error report:
SQL Error: ORA-02443: Cannot drop constraint - nonexistent constraint
02443. 00000 - "Cannot drop constraint - nonexistent constraint"
*Cause:    alter table drop constraint <constraint_name>
*Action:   make sure you supply correct constraint name.
What can I do to get past this so I can perform the following insert and receive this error message??
insert into CPULIST
values ('CPU1', 'P2', SYSTIMESTAMP, SYSTIMESTAMP);
Error starting at line 1 in command:
insert into CPULIST
values ('CPU1', 'P2', SYSTIMESTAMP, SYSTIMESTAMP)
Error report:
SQL Error: ORA-00001: unique constraint (APSOM.XPKCPULIST) violated
00001. 00000 - "unique constraint (%s.%s) violated"
*Cause:    An UPDATE or INSERT statement attempted to insert a duplicate key.
For Trusted Oracle configured in DBMS MAC mode, you may see
this message if a duplicate entry exists at a different level.
*Action:   Either remove the unique restriction or do not insert the key.

Primary Key Question

Probably a silly question - I'm fairly new to APEX and trying to design a small system. I come from a FORMS background, and would always have had my support tables with character keys e.g. Clubs - Club_code, varchar2(3), Club_name varchar2(30) with values like "ABC" and "CDE" as mnemonic primary keys. APEX seems to want a sequential PK on the tables used - is it feasible to use character PK fields, or better to go with the default functionality?
Thanks
Malcolm

Hi Mal,
like you I'm not a fan of sequence generated keys on everything, I think this was a design choice made by the Apex team in the early days of Apex (HTMLDB) when the intention was that Apex would be intended primarily for non-technical users. To me its an implementation choice and has nothing to do with relational design theory, and when working with new interfaces to existing systems, it may be a choice the developer does not have. I think it would just be simpler if the Apex developer had that choice when using the wizards.
For ordinary forms it is not too difficult.
1. Create a new page as a "Form on a Table with Report". Identify the PK field and set this as populated from an existing trigger.
2. Edit the form page that was created. Edit the item created for the PK field. Set the "Display As" property under "Name" to "text field".
3. Set the "Read Only Condition Type" property under "Read Only" to "Value of Item in Expression 1 is NOT NULL". Enter the name of the item in "Expression 1".
Now when you run the report page, depending whether the table is empty you may see some rows. Regardless, you can click on the create button and it will take you to the form page with the PK text field enterable. You can enter a row of data and click create and you are taken back to the report page. Now when you click the edit link for a row in the report you will see that you are taken to the form page with the PK field is now Read Only. (Correct behaviour as PKs should not be updateable)
Depending how you specified the link in the report page, you may also want to change the PK column to show the value of the column rather than an edit graphic. This can be done by editing the report page and then editing the Report Attributes of the report region. Edit the PK column from the list of columns and set the Link Text in the Column Link to the column name surrounded by # character. ie #P30_COL_NAME#. This can be quickly achieved by clicking the column name quick link just below.
Unfortunately there is easy fix with the tabular forms wizard. You either have to create new Multi Row Update processes or possibly use the updateable views and instead of triggers method.
Regards
Andre

How to find out the primary key column of a database table?

Hi
Given the following scenario :
Given an inputfield, the user can enter a table name. The code behind will base on the table name given and extract out the fieldname of the primary key and concatenate the two field to become a unique string.
Eg. Order ID and Product ID make out a primary key.
How do i achieve that? Any code sample?
Regards,
Rayden

Check the below code :
REPORT zTest no standard page heading.
data : i_DD03P like DD03P occurs 0 with header line.
data v_table like DCOBJDEF-NAME.
parameters : p_table like dd02l-tabname.
start-of-selection.
v_table = p_table.
CALL FUNCTION 'BDL_DDIF_TABL_GET'
EXPORTING
    NAME                = v_table
   STATE               = 'A'
   LANGU               = 'E'
IMPORTING
GOTSTATE            =
DD02V_WA            =
DD09L_WA            =
TABLES
   DD03P_TAB           = i_DD03P
DD05M_TAB           =
DD08V_TAB           =
DD12V_TAB           =
DD17V_TAB           =
EXCEPTIONS
   ILLEGAL_INPUT       = 1
   OTHERS              = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
loop at i_DD03P.
if i_dd03p-KEYFLAG = 'X'.
write:/ 'Key fields', i_dd03p-FIELDNAME.
endif.
endloop.
Thanks
Seshu

For the Primary Key Field with the combination of other fields

Hai
I Have a problem in creating trigger for the following
the problem goes like this..
i have a table with the fields
fld1 (varchar2(6) fld2(varchar2(20)) fld3 (number)
the fld1 is a primary key.
here in this table i am inserting the values ..
At the time of inserting the fld1 should get the part value of fld2
say if new value for fld2 is "SAM & CO" then
it should take the first letter and then followed by the sequence..
i.e., the fld1 is the combination of a
letter + firt letter of the fld2 + sequence
fld1 fld2 fld3
CS001 SSSSS 324234
CP001 PPPPP 5345435
CS002 SSSS 53543543
Here the Sequence should vary depending on the alphabet of the fld1
if P the the Sequence should be the next number of fld1 to P
i.e.,
if i add the value like this
insert into tname(fld2,fld3) values('PQQQQ',34343)
then it should be inserted as
CP002 PQQQQ 34343
I need the solution for this..
Thanx
Gaya3
thanx
gaya3

There are not enough details to be sure since you have not provided the mappings. From just the error, it looks like you are using the tableC.tableA_ID field as the foreign key in the ManyToOne relationship to A, but have marked it as insertable=false, writeable=false, meaning that it cannot be updated or used for inserts.
Either make it writable (set the settings to true), or add another basic mapping/attribute in the entity for TableC that maps to the field which you can use to set when you insert a new tableC entity. A simple example is available at
http://wiki.eclipse.org/EclipseLink/Examples/JPA/2.0/DerivedIdentifiers
Best Regards,
Chris

Primary Key Issue With Creating Tables

Hi,
I have the following scripts to create my two tables in oracle 10g, i was wondering wether or not i had correctly set up my primary key or if there is a better way of doing it than the way i have.
Here are my two scripts for my tables:
CREATE TABLE CUSTOMER (
fname varchar2(15) NOT NULL,
lname varchar2(20) NOT NULL,
age varchar2(3) NOT NULL,
custAreaCode number(5) NOT NULL,
custNumber number(6) NOT NULL,
constraint cust_pk PRIMARY KEY (custAreaCode),
constraint cust_pk2 PRIMARY KEY (custNumber),
constraint age_chk CHECK (age >=18 AND age <150)
CREATE TABLE PHONECALL (
startDateTime smalldatetime NOT NULL,
custAreaCode number(5) NOT NULL, ---Reference PK From Customer Table
custNumber number(6) NOT NULL, ---Reference PK From Customer Table
dialledAreaCode number(5) NOT NULL,
dialledNumber number(6) NOT NULL,
crgPerMinute number number (3,1) NOT NULL,
endDateTime smalldatetime NOT NULL));
I am not sure if i have referenced the primary keys correctly in the PHONECALL table.
Thanks in advance :)

Hi,
You want like this below ? I think that smalltime data type is not a valid type. Other thing, this is not a rule, but I advice you to put the primary key columns as the first columns of your table. One question: There is no PK on the phonecall table ?
SGMS@ORACLE10> create table customer (
2 custareacode number(5) not null,
3 custnumber number(6) not null,
4 fname varchar2(15) not null,
5 lname varchar2(20) not null,
6 age varchar2(3) not null,
7 constraint cust_pk primary key (custareacode),
8 constraint cust_uk unique (custnumber),
9 constraint age_chk check (age >=18 and age <150)
10 );
Table created.
SGMS@ORACLE10> create table phonecall (
2 custareacode number(5) not null constraint fk_phone_cusarecode_customer references customer,
3 custnumber number(6) not null constraint fk_phone_custnumber_customer references customer,
4 startdatetime date not null,
5 dialledareacode number(5) not null,
6 diallednumber number(6) not null,
7 crgperminute number (3,1) not null,
8 enddatetime date not null);
Table created.
SGMS@ORACLE10> select table_name,constraint_name,constraint_type from user_constraints
2 where table_name in ('CUSTOMER','PHONECALL') and constraint_type in ('P','U','R');
TABLE_NAME                     CONSTRAINT_NAME                C
CUSTOMER                       CUST_PK                        P
CUSTOMER                       CUST_UK                        U
PHONECALL                      FK_PHONE_CUSARECODE_CUSTOMER   R
PHONECALL                      FK_PHONE_CUSTNUMBER_CUSTOMER   RCheers

Sequenced primary key slowed down my database!

I have a table (11 million rows) which was extremely slow for searches (more than 30 seconds) and I thought it's because the records were not unique and I did not have primary key for it. So I decided to add a column and put a sequence in it with a trigger for inserts that fills the field as a primary key. I also updated the statistics for the table. But this alone made the searches a lot slower. Just a sorting takes more than 10 minutes now. Does anybody have any idea what could have gone wrong?!
I'm working with application express 4.1 and oracle 11g if that matters.
I appreciate any help.

I don't know if this helps:
SQL> show parameter optimizer
NAME                                 TYPE        VALUE
optimizer_capture_sql_plan_baselines boolean     FALSE
optimizer_dynamic_sampling           integer     2
optimizer_features_enable            string      11.2.0.1
optimizer_index_caching              integer     0
optimizer_index_cost_adj             integer     100
optimizer_mode                       string      ALL_ROWS
optimizer_secure_view_merging        boolean     TRUE
optimizer_use_invisible_indexes      boolean     FALSE
optimizer_use_pending_statistics     boolean     FALSE
optimizer_use_sql_plan_baselines     boolean     TRUE
SQL> show parameter db_file_multi
NAME                                 TYPE        VALUE
db_file_multiblock_read_count        integer     64
SQL> show parameter db_block_size
NAME                                 TYPE        VALUE
db_block_size                        integer     8192
SQL> show parameter cursor_sharing
NAME                                 TYPE        VALUE
cursor_sharing                       string      EXACT
SQL> column sname format a20
SQL> column pname format a20
SQL> column pval2 format a20
SQL>
SQL> select
2 sname
3 , pname
4 , pval1
5 , pval2
6 from
7 sys.aux_stats$;
SNAME                PNAME                     PVAL1 PVAL2
SYSSTATS_INFO        STATUS                          COMPLETED
SYSSTATS_INFO        DSTART                          04-02-2010 14:19
SYSSTATS_INFO        DSTOP                           04-02-2010 14:19
SYSSTATS_INFO        FLAGS                         1
SYSSTATS_MAIN        CPUSPEEDNW           1683.65129
SYSSTATS_MAIN        IOSEEKTIM                    10
SYSSTATS_MAIN        IOTFRSPEED                 4096
SYSSTATS_MAIN        SREADTIM
SYSSTATS_MAIN        MREADTIM
SYSSTATS_MAIN        CPUSPEED
SYSSTATS_MAIN        MBRC
SNAME                PNAME                     PVAL1 PVAL2
SYSSTATS_MAIN        MAXTHR
SYSSTATS_MAIN        SLAVETHR
13 rows selected.

Primary key question with PHPmysql database

Similar Messages

Maybe you are looking for