Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 5955003
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 22, 20262026-05-22T18:03:07+00:00 2026-05-22T18:03:07+00:00

Let us say we have the following table structure and values: FooTable: foo1 foo2

  • 0

Let us say we have the following table structure and values:

FooTable:
    foo1    foo2   timestamp
     1       1      1
     2       2      1
     2       1      2

Currently there is no primary key constraint on the table.

Question:

In Oracle, what is the best way to make foo1 the primary key of the table? Assume that:

  1. No two rows will have both the same timestamp and foo1 value
  2. The row with the latest timestamp takes precedence (other rows with the same foo1 value should be deleted).

Thus, here is the desired table structure after the query:

FooTable:
    foo1(pk)  foo2   timestamp
     1         1      1
     2         1      2

Note: The main problem is deleting the old duplicate rows. Once this is done, the following query can be used to setup the primary key without fear of duplicates:

alter table FooTable modify foo1 primary key;

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-22T18:03:08+00:00Added an answer on May 22, 2026 at 6:03 pm

    Keep in mind that you’re destroying data here. Make sure that you have a good back-up of the database.

    I don’t work with Oracle, but I think that this is generic enough. I don’t know if Oracle allows table aliases in the DELETE clause or not, so you may need to adjust for that:

    DELETE FT1
    FROM FooTable FT1
    WHERE EXISTS (
        SELECT *
        FROM FooTable FT2
        WHERE
            FT2.foo1 = FT1.foo1 AND
            FT2.timestamp > FT1.timestamp
    )
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Let's say I have to following table with values (1st row is the description)
I have table with following structure id int auto increment, primary key uid int
Let's say I have the following hypothetical data structure: create table country ( country_id
I have the following structure: Table: products id, name, sort_order Let's say I only
Let's say I have the following table: CustomerID ParentID Name ========== ======== ==== 1
Let's say I have the following simple table variable: declare @databases table ( DatabaseID
Let's say I have the following database table: record_id | record_date | record_value -----------+-------------+--------------
Let's say I have the following HTML: <table id=foo> <th class=sortasc>Header</th> </table> <table id=bar>
Let's say I have a table containing following data: | id | t0 |
In PostgreSQL 8.3, let's say I have a table called widgets with the following:

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.