Cannot view primary keys in sqldeveloper 1.0.0

Hello ,
when i run the following query I do not get any results .
select * from <table_name> where company_id is NULL;
But when I run this
select * from <table_name> ;
I cannot see anything in company_id column for the record results I get. company_id is the primary key so there is no way it can be null . But why am I not able to see the data for this column in sql developer ?
Thanks,
Neelima

nemikkil wrote:
Hello ,
when i run the following query I do not get any results .
select * from <table_name> where company_id is NULL;
But when I run this
select * from <table_name> ;
I cannot see anything in company_id column for the record results I get. company_id is the primary key so there is no way it can be null . But why am I not able to see the data for this column in sql developer ?
Thanks,
Neelimaselect CONSTRAINT_NAME,constraint_type,TABLE_NAME from user_constraints where table_name='YOUR_TABLENAME';
SHOW The output of above query and select * from your_tablename ;
select * from <table_name> where company_id is NULL;
show the output here.

Similar Messages

Having a problem with creating/using a primary key on a view

I have a problem with a primary key on a view
I created the view and primary key as follows:
CREATE OR REPLACE FORCE VIEW "MDD"."ROCK_LU" ("DESCRIPTION",
UNIQUE ("DESCRIPTION") RELY DISABLE,
CONSTRAINT "ROCK_LU_PK" PRIMARY KEY ("DESCRIPTION") RELY DISABLE) AS
SELECT DESCRIPTION
FROM MRMC_LU
WHERE ROCK = 'T';
The view with the primary key appears to have been created as there were no error messages. (The above was from the sql tab in sql developer.)
When I try to create the foreign key on my mdd_hr table - I get an error
/* hr_name - foreign key */
ALTER TABLE mdd_hr add CONSTRAINT hr_name_fk FOREIGN KEY (hr_name) REFERENCES rock_lu(description);
Error report:
SQL Error: ORA-02270: no matching unique or primary key for this column-list.
When I lookup the index in sql developer, rock_lu_pk is not there.
All my other foreign keys work - but I don't understand what I am doing wrong with this one. Please help.
glenn
Background - as to why I want to use a view as a lookup table.
The MRMC_LU table that the view is created from is structured like:
DESCRIPTION - MINERAL - ROCK - MODIFIER - COMMODITY
ANHYDRITE - T - T - T
APLITE - T - - T
GRAPHITE - T - - - T
GREYWACKE - - T
DESCRIPTION is a list of all names of minerals, rocks, modifiers and commodities. T is entered in each valid field. Often a description name is used for both a mineral and a rock or a mineral and a commodity or any other combination. Because this database is just starting up, it was more efficient to create one table that could be updated (and thereby automatically update the MINERAL_LU, ROCK_LU, MODIFIER_LY, COMMODITY_LU views) rather than create and maintain four separate but similar tables. A primary key cannot be generated for the MRMC_LU table as there are nulls in each column
except DESCRIPTION.
Perhaps there is a smarter way to do this?

http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96540/statements_85a.htm#2065512
You can specify constraints on views and object views. You define the constraint at the view level using the out_of_line_constraint clause. You define the constraint as part of column or attribute specification using the inline_constraint clause after the appropriate alias.
Oracle does not enforce view constraints. However, operations on views are subject to the integrity constraints defined on the underlying base tables. This means that you can enforce constraints on views through constraints on base tables.
Restrictions on View Constraints
View constraints are a subset of table constraints and are subject to the following restrictions:
You can specify only unique, primary key, and foreign key constraints on views. However, you can define the view using the WITH CHECK OPTION clause, which is equivalent to specifying a check constraint for the view.
Because view constraints are not enforced directly, you cannot specify INITIALLY DEFERRED or DEFERRABLE.
View constraints are supported only in DISABLE NOVALIDATE mode. You must specify the keywords DISABLE NOVALIDATE when you declare the view constraint, and you cannot specify any other mode.
You cannot specify the using_index_clause, the exceptions_clause clause, or the ON DELETE clause of the references_clause.
You cannot define view constraints on attributes of an object column.
Rgds.

Problem with object view with primary-key based object identifier

Hello!
I met such problem.
t1 is persinstent-capable class:
class t1 : public PObject { .... };
T1OV is object view, based on object table T1OT
I1 is primary key of the table T1OT.
Next code:
t1* t = new (conn, "T1OV") t1(...);
conn->commit();
try
t->markDelete();
conn->commit(); // exception throws here
Works fine if T1OV defined as:
create view t1ov of t1 with object identifier default
as select * from t1ot;
And throws an exception
"ORA-22883: object deletion failed"
if:
create view t1ov of t1 with object identifier (I1)
as select * from t1ot;
Such problem also occurs when object view is based on relational table/view (OID is primary-key based).
Also it occurs when
t->markModified() used insted of t->markDelete()
I am using Oracle 9i second release for windows and
MS VC++
Thank You

http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96540/statements_85a.htm#2065512
You can specify constraints on views and object views. You define the constraint at the view level using the out_of_line_constraint clause. You define the constraint as part of column or attribute specification using the inline_constraint clause after the appropriate alias.
Oracle does not enforce view constraints. However, operations on views are subject to the integrity constraints defined on the underlying base tables. This means that you can enforce constraints on views through constraints on base tables.
Restrictions on View Constraints
View constraints are a subset of table constraints and are subject to the following restrictions:
You can specify only unique, primary key, and foreign key constraints on views. However, you can define the view using the WITH CHECK OPTION clause, which is equivalent to specifying a check constraint for the view.
Because view constraints are not enforced directly, you cannot specify INITIALLY DEFERRED or DEFERRABLE.
View constraints are supported only in DISABLE NOVALIDATE mode. You must specify the keywords DISABLE NOVALIDATE when you declare the view constraint, and you cannot specify any other mode.
You cannot specify the using_index_clause, the exceptions_clause clause, or the ON DELETE clause of the references_clause.
You cannot define view constraints on attributes of an object column.
Rgds.

Cannot modify value of primary key field after lookup.

I realize this could be a WebSphere problem, but I don't know if it is an EJB problem or what? So I'm posting anyway, and adding Duke Dollars in the hopes someone out there has encountered this.
Okay, I'm using WebSphere Studio Application Developer 4.0.3.
I am using an EJB that has three primary key fields.
I use the primary keys to lookup the bean.
I then want to update the value of one of the primary keys.
So I create a setter and getter method for that primary key field.
I then can call the set method, but it does nothing.
I get no errors.
It compiles.
I rebuild, regenerate access beans, and redeploy and rmic.
I can use ctrl-space to see the functions in the JSP editor.
However, the set function never gets called for some reason, and I get no runtime exception either.
For example, if I do this in my code:
MyBeanFactory myBean = new MyBeanFactory();
MyBeanKey myBeanKey = new MyBean(name,age,city);
MyBean myBean = myBeanFactory.findByPrimaryKey(myBeanKey);
// this function doesn't do anything, because it's a primary key field
// but it does compile and I get no runtime errors
myBean.setCity("Orlando");
// this function works fine, presumably because it isn't a primary key
myBean.setState("Florida");Questions;
Is there a restriction that says I can't update the value of a field if it is marked as a primary key?
If not, what could I be doing wrong?

Looks like your appserver is working as per the specification.
Check this out:
Question
How can I update the primary key field in a CMP Entity Bean?
Derived from
A question posed by Shanks75 shanks75
Topics
Java:API:EJB:EntityBean:CMP, Java:API:EJB:2.0
Author
Tim Duggan
Created
Oct 9, 2001
Answer
You cannot change the primary key field of an Entity bean. Refer to page 130 of the EJB 2.0 specification, it states "Once the
primary key for an entity bean has been set, the Bean Provider must not attempt to change it by use of set accessor methods
on the primary key cmp-fields. The Bean provider should therefore not expose the set accessor methods for the primary key
cmp-fields in the component interface of the entity bean."
A work around to update a primary key field, would be to remove and then an re-create the bean.
taken from here:
http://www.jguru.com/faq/view.jsp?EID=515864

[SQL Server]Violation of PRIMARY KEY constraint 'DeploymentSummary_PK'. Cannot insert duplicate key in object 'dbo.DeploymentSummary'. The duplicate key value is

I have migrated my SCCm 2007 environment to SCCM 2012 SP1 CU4.
I noticed in the System Status\Component Status\SMS_STATE_SYSTEM a lot of errors like the one below:
Microsoft SQL Server reported SQL message 2627, severity 14: [23000][2627][Microsoft][SQL Server Native Client 11.0][SQL Server]Violation of PRIMARY KEY constraint 'DeploymentSummary_PK'. Cannot insert duplicate key in object 'dbo.DeploymentSummary'. The duplicate key value is (1, 0, S0220438, 0). : spUpdateClassi
Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information.
When looking up the deployment ID and recreate the Deployment the problem is solved. But I have 700 packages and don't want to manually do this action on all packages. I think it is related to the migration i did and something went wrong there :-(
Besides it will retriggers the deployment to the clients which is also not preferred.
Is there another way to solve this by e.e.g do something directly in the SQL database tables ?

Hi,
It is not supported by Microsoft that do something directly in SQL database.
If you want to do that, you could make a call to CSS.
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

View Objects with Union Queries--trouble with primary keys

Hi,
I'm working with JDev 11.1.1.3 and am trying to do a couple of things (without success--yet). I am trying to create a master-detail relationship that displays the existing data in a set of 3 tables and later I will be creating forms for inserting and updating.
The table structure is like this:
Table: Member
Field: MemberIdx (PK)
Field: Data
Table: CfgPartner
Field: MemberIdx (PK)
Field: DocType (PK)
Field: DocRevision (PK)
Field: OtherData
Table: CfgB2BPartner
Field: MemberIdx (PK)
Field: DocType (PK)
Field: DocRevision (PK)
Field: B2BData
I have a View Object for the master table (Member). And I have created a 2nd View Object that is a union of the other two tables. There is some data in CfgPartner that doesn't have a matching record in CfgB2BPartner and vice versa. My thinking is that the two tables are related and I would like them to display within the same table on the ADF page.
My 2nd View Object has this query:
SELECT CfgPartner.MEMBERIDX,
CfgPartner.DOCTYPE,
CfgPartner.DOCREVISION,
CfgPartner.OTHERDATA,
CfgB2bpartner.B2BDATA
FROM CFG_PARTNER CfgPartner, CFG_B2BPARTNER CfgB2bpartner
WHERE CfgPartner.MEMBERIDX=CfgB2bpartner.MEMBERIDX(+)
and CfgPartner.DOCTYPE=CfgB2bpartner.DOCTYPE(+)
and CfgPartner.DOCREVISION=CfgB2bpartner.DOCREVISION(+)
UNION
SELECT CfgB2bpartner.MEMBERIDX AS MEMBERIDX1,
CfgB2bpartner.DOCTYPE AS DOCTYPE1,
CfgB2bpartner.DOCREVISION AS DOCREVISION1,
CfgPartner.OTHERDATA,
CfgB2bpartner.B2BDATA
FROM CFG_PARTNER CfgPartner, CFG_B2BPARTNER CfgB2bpartner
WHERE CfgB2bpartner.MEMBERIDX=CfgPartner.MEMBERIDX(+)
and CfgB2bpartner.DOCTYPE=CfgPartner.DOCTYPE(+)
and CfgB2bpartner.DOCREVISION=CfgPartner.DOCREVISION(+)
ORDER BY MEMBERIDX,DOCTYPE,DOCREVISION
The query is valid and runs fine in the database. However, the error I'm getting in the app module makes it sound like I don't have my primary keys set up correctly. Here is the error: (oracle.jbo.PersistenceException) JBO-26028: View object testCfgPtnrCfgB2BPtnr does not include a primary key attribute Memberidx of entity base CfgB2bpartner.
In the View Object it shows the attributes Memberidx, Doctype, Docrevision, Memberidx1, Doctype1, and Docrevision1 all as key attributes. The only strange thing I see is the Entity Usage for Memberidx1, Doctype1, and Docrevision1 are all empty and the info column says "Transient".
Any help would be appreciated.
-Steve

Hi,
I think that to achieve this you need to suround it with another "select from" statement and create alias for the columns
I created a test with the departments table (assuming that they are two different tables with different attributes) just to see that it works.
SELECT DEPID1,DEPID2,DEPNAME1,DEPNAME2
FROM(
SELECT Departments1.DEPARTMENT_ID AS DEPID1,
           NULL as DEPID2,
       Departments1.DEPARTMENT_NAME AS DEPNAME1,
          NULL as DEPNAME2
FROM DEPARTMENTS Departments1
UNION
SELECT Departments2.DEPARTMENT_ID AS DEPID2,
          NULL as DEPID1,
       Departments2.DEPARTMENT_NAME AS DEPNAME2,
         NULL as DEPNAME1
FROM DEPARTMENTS Departments2)The resulting VO will have 4 attributes and you can set the primary key to be (DEPID1,DEPID2)
If your 2 tables have common columns then these columns can have the same alias
If you have any problems let me know :)
Gabriel.

IR - if count (primary key) cannot change to count different column

Apex 4.1.1.00.23 Windows 7 IE8 / Firefox 16
If I add a Group By and Count to an Interactive report and choose the primary key column as the one to Count, run the report and then edit the Group By to count a different column, the result set does not change, and if I edit the Group By again it shows that the Counted column has reverted back to the primary key column.
If I initially choose a different column I can change it and rerun the report successfully, but once I choose the primary key column it cannot be changed. This seems to happen on all applications and all browsers. Is it a bug in Apex?
Thanks,
Nick.

I've tried this in 4.1.0.00.32: works normally. In 4.1.1.00.23 however i'm getting the weird behaviour: you can count on any column, but the moment you count the same column as the one grouped on you can not change the column back to another one anymore. Something which works fine in 4.1.0.00.32.

How do I obtain the next number for a Primary Key using an ADF View Object?

I have two separate View Objects (A & B) for the same Entity Object. View Object A does a SELECT on all of the fields in the table. This View Object is where I execute my adds and updates. View Object B is only used to retrieve the next number for the primary key. This is done so that when I add a row to the database, I always get the max number of the primary key and add one to it. I accomplished this by setting the SQL mode to Expert and using the SQL: "SELECT MAX(NBR) AS MAX_NUMBER FROM TABLE_1". This may be overkill having a seperate View Object for this, but so far this is the only way I have found to obtain the next number. However, I have discovered that this way does not always work.
The problem I'm running into is when I try to add multiple records to View Object A without committing the transaction between each add. Because View Object B is disconnected from View Object A, the MAX_NUMBER of View Object B comes back with the same number for each add I do on View Object A. So I know I must retrieve the MAX_NUMBER from View Object A.
I've tried using the following code in my Table1ViewImpl class:
this.setQuery("SELECT MAX(Table1.NBR) AS MAX_NUMBER FROM TABLE_1 Table1");
this.executeQuery();
The view object now has what I want, but I have yet to figure a way to extract the MAX_NUMBER out of the View Object. I've also looked into using the method addDynamicAttribute() but I can't figure out any way to set the attribute with the MAX_NUMBER.
I can't be the only one trying to retrieve the next number from a database table using ADF. Can anyone help me with this? FYI - I'm using JDev 10.1.3 EA.

You missing the point.
On a multi-user db knowing the next highest number doesn't guarantee the number will be available when it comes time to commit the record. You can prove this to yourself by opening two instances of your app and do whatever you do to add a new record to your VO. Both will assume the same number, and when you commit an error will be generated
You must use sequences to avoid the possibility of duplicate keys. If you are trying to avoid gaps in your numbering then you need to convince yourself why this is necessary.

How to speed up fast refresh of materialized view without primary key

Thought I'd share this info, as I couldn't find anything on here to help me diagnose the issue:
I had a materialized view that was taking longer to perform a fast refresh than it took to perform a complete refresh. My mview had no primary key, as the base table had no primary key.
I created a trace file for the session and saw references to a column M_ROW$$ in my mview. Nowhere in the data dictionary could I find a reference to the m_row$$ column in my mview, but apparently it exists and is created automatically. After creating the index below, the fast refresh took 6 minutes to add 500k rows to the materialized view. (versus 4+ hours without the index) When I looked in the trace file, I noticed that for each row in the mview log, it first tries to update the mview with an UPDATE statement, then it performs an insert of the new data. Seems like it should be able to determine whether to perform an update or insert based on the DMLTYPE$$ column of the mview log. What was killing my performance was the UPDATE phase. Since I had no primary key on the mview, and no index on the m_row$$ column, the UPDATE phase was performing a full table scan of my mview for every row in the mview log. I was expecting it to be smart enough to only perform inserts, as the only transactions against the base table were inserts.
In summary: If you have a materialized view without a primary key, create an index on the m_row$$ column of the mview, even though no such column displays in the data dictionary.
ex:
CREATE MATERIALIZED VIEW mv_minidrr ...
CREATE INDEX pk_mv_minidrr ON mv_minidrr(m_row$$) ...

Well, there indeed is a column called M_ROW$$
Your MLOG$_EMP is nothing but the materialized view log on the base table.
SQL> create materialized view log on emp with rowid ;
Materialized view log created.
SQL> create materialized view emp_mview refresh fast on demand with rowid as select * from emp ;
Materialized view created.
SQL> desc mlog$_emp
Name                                                  Null?    Type
M_ROW$$                                                        VARCHAR2(255)
SNAPTIME$$                                                     DATE
DMLTYPE$$                                                      VARCHAR2(1)
OLD_NEW$$                                                      VARCHAR2(1)
CHANGE_VECTOR$$                                                RAW(255)
SQL> select table_name, column_name from user_tab_columns where column_name = 'M_ROW$$' ;
TABLE_NAME                     COLUMN_NAME
MLOG$_EMP                      M_ROW$$
1 row selected.
SQL>

Create a materized view without primary key constraint on the base table?

Hi
I tried to create a materized view but I got this error:
SQL> CREATE MATERIALIZED VIEW TABLE1_MV REFRESH FAST
START WITH
to_date('04-25-2009 03:00:13','MM-dd-yyyy hh24:mi:ss')
NEXT
sysdate + 1
AS
select * from TABLE1@remote_db
SQL> /
CREATE MATERIALIZED VIEW TABLE1_MV REFRESH FAST
ERROR at line 1:
ORA-12014: table 'TABLE1' does not contain a primary key constraint.
TABLE1 in remote_db doesn't have a primary key constraint. Is there anyway that I can create a materized view on a base table which doesn't have a primary key constraint?
Thanks
Liz

Hi,
Thanks for your helpful info. I created a materialized view in the source db with rowid:
SQL> CREATE MATERIALIZED VIEW log on TABLE1 with rowid;
Materialized view log created.
Then I created a MV on the target DB:
CREATE MATERIALIZED VIEW my_schema.TABLE1_MV
REFRESH FAST
with rowid
START WITH
to_date('04-25-2009 03:00:13','MM-dd-yyyy hh24:mi:ss')
NEXT
sysdate + 1
AS
select * from TABLE1@remote_db
SQL> /
CREATE MATERIALIZED VIEW my_schema.TABLE1_MV
ERROR at line 1:
ORA-12018: following error encountered during code generation for
"my_schema"."TABLE1_MV"
ORA-00942: table or view does not exist
TABLE1 exists in remote_db:
SQL> select count(*) from TABLE1@remote_db;
COUNT(*)
9034459
Any clue what is wrong?
Thanks
Liz

Materialized View - does not contain a primary key constraint

I am trying to create materialized view. I gone through the MV wizard creation. Added 2 columns (foo_column, foo_pk) of the table and have a simple select statement (Select foo_column from foo_dim). Also created a primary key contrainst and refencing the primary key (FOO_PK) of the dimension.
I am getting the following error:
ORA-12014: table 'FOO_DIM' does not contain a primary key constraint

It was solved. The table that I am querying has to have a primary key defined before creating a materialized view.

Key in View for two primary keys tables

Hi
I have some view joining LIKP and LIPS:
LIKP -   Primary Key MANDT, VBELN
LIPS -   Primary Key MANDT, VBELN, POSR
The Key for the LIKP-LIPS View is:
MANDT      LIKP
VBELN       LIKP
MANDT_I    LIPS
VBELN_I    LIPS
POSNR_I   LIPS
So, for that Key, if i need to acces a specify LIPS detail record , must i fill all the keys in the where (filling VBELN twice) like this:
WHERE VBELN = vbvalue AND VBELN_I = vbvalue AND POSNR_I = posvalue ?
How must i make the Select for acces this View using its Key ?
Regards
Frank

Hi
Just as I said:
SELECT SINGLE * FROM Z<VIEW> WHERE VBELN = <VBELN>
                                                            AND POSNR_I = <POSNR>.
Anyway it's should be better you correct the view deleting the field MANDT_I, VBELN_I, if you can't, I believe the select above works fine.
VIEW FIELDS:
View Field Table Field Key
MANDT LIKP MANDT Yes
VBELN LIKP VBELN Yes
<b>MANDT_I LIPS MANDT Yes <----- WRONG
VBELN_I LIPS VBELN Yes      <----- WRONG</b>
POSNR_I LIPS POSNR Yes
ERNAM LIKP ERNAM
ERDAT LIKP ERDAT
VKORG LIKP VKORG
PSTYV_I LIPS PSTYV
MATNR_I LIPS MATNR
WERKS_I LIPS WERKS
LGORT_I LIPS LGORT
By this defintion the field MANDT and VBELN are only twice, but it doesn't mean the record is double in the VIEW.
So it you have the delivery 100 with 3 items in the client 200, in the view you'll see:
Record 1: MANDT   = 200
               VBELN    = 0000000100
               MANDT_I = 200
               VBELN_I = 0000000100
               POSNR_I = 000010
Record 2: MANDT   = 200
               VBELN    = 0000000100
               MANDT_I = 200
               VBELN_I = 0000000100
               POSNR_I = 000020
Record 3: MANDT   = 200
               VBELN    = 0000000100
               MANDT_I = 200
               VBELN_I = 0000000100
               POSNR_I = 000030
Max

Primary Key Materlized View and primary key in master tables

We are using Oracle 11g2 and I created a materlized view on several master tables. The master tables all have primary key, but I did not include all primary key columns in the defining query.
According to Oracle Manual e10592 Specify WITH PRIMARY KEY to create a primary key materialized view. This is the default ....
The master table must contain an enabled primary key constraint, and the defining query of the materialized view
must specify all of the primary key columns directly.My MV created OK and works. My question is what can be the impact on my MV? Could it hit the performance. It takes 40 minutes for the MV to be created and 5 minutes to refresh for single row insert in each mater table. I would like to see it refresh in seconds.

Retrieving rows from the mview is purely a function of the number of rows and indexing on the mview itself. Refreshing the mview wall time depends on the quality of the query used to refresh the mview. Whether you include PKs from the source table in the mview is of little, or no, consequence here. What matters is the execution path of the refresh query. Is there proper indexing on the underlying tables to support the joins. Did you use mlog$_s to enable fast refresh - are mlog$_s even usable for your mview. There are a number of possible causes to your problem and we do not have enough information to make an estimate of the problem.
BTW, if the mview could refresh in seconds w/o mlog$_s, you probably do not need an mview.

Materialized View and Primary Key

Hoping that this is just a simple question. I create a materialized view however when trying to refresh and run logs Oracle gives me an error that there is no Primary Key. How do I specify a collumn or collumns as a primary key?

Hi,
I hope this link help you
http://girlgeek-oracle.blogspot.com/2008/01/materialized-views.html
Regrds Salim.

Creating a view with a primary key

I want to create a view with a defined primary key. I understand
the view is created within a select statement, but do not
understand how you would define a particular field as a primary
key in the view. Also if your select statement attempts to build
the view and has duplicate keys in the select result set, what
would happen when the duplicate key is found? Would it just not
include the duplicate key in the view?
Thanks in advance for your help.
-Pat

I have a rather difficult problem with duplicate invoice numbers
contained in unique records. In other words I have many records
that appear as follows:
3593, 0004009090, CUSTOMER, TAX, 20000117,014011976-01
4411, 0004009090, CUSTOMER, TAX, 20000718,014011976-01
The last field is invoice number '014011976-01' In my case I am
building a flat file using UTL_FILE for loading into SAP
Business Warehouse. In SAP I need to have Invoice number as a
key in which case I can't have duplicate invoice numbers. All
the SQL I have tried to date returns a large amount of records
similar to the above records. I am selecting these records from
4 different schemas which represent 4 different companies. I
realize the data is the problem and that the vendor of the
product I am working with should not allow records with
duplicate invoice numbers, but I have to get the data loaded as
that is what they want and are paying for. So back to my View. I
was hoping to create a view and be able to work in the view to
remove duplicate records prior to writing them to a file. Any
suggestions are welcomed.
Thanks
-Pat

Cannot view primary keys in sqldeveloper 1.0.0

Similar Messages

Maybe you are looking for