What is VIEW in Database table what is the advantage

Hi:
I would like to get your opinion on what is the advantage of Table VIEW?
I read a note saying it is all about simplifying Query.
But when you come to XMLTYPE where there is only ONE ROW and NO COLUMN,
How do you create XMLVIEW for a large XML files?
Please help
Ali_02

Overview of Views
Read here...
http://download.oracle.com/docs/cd/E11882_01/server.112/e10713/schemaob.htm#i20690
XMLView or XMLTYPE ?
Overview of XML in Oracle Database
Read here...
http://download.oracle.com/docs/cd/E11882_01/server.112/e10713/cncptdev.htm#CNCPT1535
Edited by: ordba on Mar 4, 2010 9:50 AM

Similar Messages

What are the advantages of using an internal table with workarea

Hi,
can anyone tell me
What are the advantages of using an internal table with workarea
over an internal table with header line?
thnks in adv
regards
nagi

HI,
Internal tables are a standard data type object which exists only during the runtime of the program. They are used to perform table calculations on subsets of database tables and for re-organising the contents of database tables according to users need.
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb35de358411d1829f0000e829fbfe/content.htm
Difference between Work Area and Header Line
While adding or retrieving records to / from internal table we have to keep the record temporarily.
The area where this record is kept is called as work area for the internal table. The area must have the same structure as that of internal table. An internal table consists of a body and an optional header line.
Header line is a implicit work area for the internal table. It depends on how the internal table is declared that the itab will have the header line or not.
e.g.
data: begin of itab occurs 10,
ab type c,
cd type i,
end of itab. " this table will have the header line.
data: wa_itab like itab. " explicit work area for itab
data: itab1 like itab occurs 10. " table is without header line.
The header line is a field string with the same structure as a row of the body, but it can only hold a single row.
It is a buffer used to hold each record before it is added or each record as it is retrieved from the internal table. It is the default work area for the internal table
1) The difference between
whih header line and with out heater line of internal table.
ex:-
a) Data : itab like mara occurs 0 with header line.
b) Data: itab like mara occurs 0.
-While adding or retrieving records to / from internal table we have to keep the record temporarily.
-The area where this record is kept is called as work area for the internal table.
-The area must have the same structure as that of internal table. An internal table consists of a body and an optional header line.
-Header line is a implicit work area for the internal table. It depends on how the internal table is declared that the itab will have the header line or not.
a) Data : itab like mara occurs 0 with header line.
table is with header line
b) Data: itab like mara occurs 0.
table is without header line
2)work area / field string and internal table
which one is prefarable for good performance any why ?
-The header line is a field string with the same structure as a row of the body, but it can only hold a single row , whereas internal table can have more than one record.
In short u can define a workarea of an internal table which means that area must have the same structure as that of internal table and can have one record only.
Example code:
data: begin of itab occurs 10,
ab type c,
cd type i,
end of itab. " this table will have the header line.
data: wa_itab like itab. " explicit work area for itab
data: itab1 like itab occurs 10. " table is without header line.
Regards,
Padmam.

What are the advantage of using nested table?

what are the advantages of using nested table?
and what are disadvantages of it?

BTW could you edit the following post and remove the dangerous code
Re: How to rename a database user?
Some other poor sap has just fried their database by trying it out
Re: Can I rename a user?
Message was edited by:
3360
Thank you for making the edit

What are the advantage of using Oracle Database when compare to SQL SERVER

Hi all
Please tell anyone about
what are the advantage of using Oracle Database when compare to SQL SERVER
Thanks in advance
Balamurugan S

user12842738 wrote:
Hi,
There are various differences between the two.
1. SQL Server is only Windows, but Oracle runs on almost all Platforms.
2. You can have multiple databases in SQL Server, but Oracle provides you only one database per instance.Given that the very term 'database' has s different meaning in the two products, this "difference" is absolutely meaningless.
3. SQL Server provides T-SQL for writing programs, whereas Oracle provides PL/SQLWhich means what? Both products have a procedural programming language. They named them differently, and the languages are not interchangeable. Means nothing in comparing the features/strengths/weaknesses/suitability to purpose.
4. Backup types in both are the same. (Except Oracle provides an additional backup called Logical Backup.)You make that sound like "Logical Backup" is something more than it is. It is nothing more than an export of the data and metadata. Many experts don't even consider it a backup. I'm sure SQL Server provides the same functionality though they probably call it by some other name.
5. Both provide High Availability.Well, I guess they both have a suite of features they refer to as "High Availability". But what does that really mean? The devil is in the details. Remember, the two products don't even agree on what constitutes a "database".
6. Both come in various distributions.???
>
If you are going for an Implementation, you can try SQL Server Express Edition and Oracle XE which are free to use.
Then you can choose whichever is comfortable for your needs.
Thanks.

What is the advantages of using oracle10g database?

Hi,
I didn't feel many advantages when using oracle10g.
So what is the advantages of using oracle10g database?
For common using,not for advance.It is not big different.
Thanks in advance!

For normal users versions before 10g is sufficent.But for large applications means distributed applications(grid) 10g is good one

How to view data in tables by selecting the synonym from the database objec

I could not figure out how to view data in tables by selecting the synonym from the database objects navigation tree. I had to first choose the synonym, view the details of the synonym to determine the table name, and then select the table from the database objects tree. Is this the only way available?

This functionality currently does not exist. I don't see it on the 1.1 statement of direction either, so perhaps someone from Oracle can give some insight as to when this could be expected.
Eric

What is the advantage of using IB to create XIBs/Class Objects over coding?

Hi all,
I hoping someone can provide me some pros and cons as to when I should use IB to create XIBs and/or class objects as opposed to directly coding them.
For example, if I choose Apple's Template for creating a Navigation Based Application (cocoa touch), the project creates two NIB files - MainMenu and RootViewController.
However looking at one of demo apps SimpleDrillDown, it does not have a RootViewController XIB and instead creates it via code.
Another example from the same two apps is that the template generates a "Navigation Controller" class object in the Mainmenu.xib. SimpleDrillDown does not bother with this in the XIB, but uses code to generate the controller:
- (void)applicationDidFinishLaunching:(UIApplication *)application {
// Create the navigation and view controllers
RootViewController *rootViewController = [[RootViewController alloc] init];
UINavigationController *aNavigationController = [[UINavigationController alloc] initWithRootViewController:rootViewController];
self.navigationController = aNavigationController;
[aNavigationController release];
[rootViewController release];
// Configure and show the window
[window addSubview:[navigationController view]];
[window makeKeyAndVisible];
as opposed to the template which only needs this:
- (void)applicationDidFinishLaunching:(UIApplication *)application {
// Configure and show the window
// Navigation Controller is defined in MainWindow.xib
[window addSubview:[navigationController view]];
[window makeKeyAndVisible];
So what are the advantages of each approach. Why does apple suggest one approach and yet all its demos use another.
Any thoughts, answers gratefully received.
TIA, Michael.

You can do whatever you're comfortable with, but most of the best Cocoa programmers--the ones on the Mac, I mean--recommend putting everything you can into Interface Builder.
It's a little like the difference between writing a program to do a bunch of financial calculations and using a spreadsheet. Yeah, the program can do everything the spreadsheet can--and more besides--but you'll find it far easier to create, use and modify the spreadsheet.
Interface Builder takes away a lot of completely meaningless choices ("What order should I create the objects in? How should I name the variables? How should I create their frames? What order should I set the attributes in?"), leaving you with an interface optimized for creating and arranging objects, and allowing your code to focus on what you really do need to think about--your application's logic.
(By the way--part of the reason Apple's demos don't all use Interface Builder is that the very first SDK releases didn't have it. Back then, you had to create all your views programatically. Believe me, I have no wish to go back to setting autoresize masks manually. Now get off my lawn, whippersnapper.)

What is the advantage in Maintaing the master data if it can be directly ..

Hi,
When looking for possible values in an object, I see that it has 20 possible values that can be selected while in BEx. But when I go to the object itself under the InfoObject tree(in rsa1), with a hope to maintain master data, I do not find "Maintain Master" in the context menu of the object.
1. where could the possible values that I saw in the report be coming from?
2. I understand it is possible that the object was filled as data was being loaded in some data target and that may explain why no master data was being maintained but it had values.
If that is the case, then, what is the advantage in Maintaing the master data (i.e. directly maintaing the master if it can be directly maintain through loaded files)?
Thanks

Thanks,
On 1:
so you are saying that the SID table gets populated during the transactional data load.
In the change mode of the object, I see
SID Table /BI0/Sxxxxxxx.
a)
Is this what you were referring to as the S table? How do I see the values in this SID talbe.
and can it be modified?
b)
Also, how come that the other object without "Maintain Master data" in context menu and the one with this option both have the
SID Table /BI0/S........
c)
Other than the difference I see in their context menu what should be the difference?
2.
You mentioned that the "System just creates a SID for the incoming value. "
a)
Where in the system do I see these system generated SIDs?
You noted that "But loading master data assures the masterdata attributes and texts, which are not generated while loading transactional data except for the SID"
b) If this is so important, is there a way to prevent data loads without master data
i.e. to force the maintenance of master data?
Also, isn't it possible to load the attributes of an infoobject while load data? You seem o be suggesting otherwise.
Thanks

What are the advantages..

Hi friends,
 can you please tell me what are the advantages of using MVC? because i can use ABAP Objects without using MVC.
Thanks in advance,
Regards,
Kannan.

Hi Kanna,
 For Dynamically componentised you need to use controller.In the main page you partition for what you want to present dynamically and then call controller as a response to the user.What the action you have take in case of Page flow logic(Event Handler) need to be placed in controller.
Using the MVC design pattern has the following advantages:
· Structuring BSP applications is simplified, since the view is cleanly separated from the controller and the model. This not only facilitates changing BSP applications, but also considerably improves their maintenance.
· You have the option of generating program-driven layout. The HTML/XML output is therefore created by program code instead of a page with scripting.
· Navigation using the <bsp:goto> element and call using the <bsp:call> element. The advantage of using <bsp:goto> navigation over redirect is that there is no additional network traffic. Furthermore, you remain in the same work process, which can have advantages for creating objects and memory space. The call using <bsp:call> element is more variable than adding them using INCLUDEdirective, since it is triggered at runtime.
With the call option using <bsp:call>, you can also distribute the user interface into components.
· Optimized performance due to fewer redirects.
· Intuitive and east-to-use interface for application development.
Main advantage of MVC is that you can keep these(Model View ,Controller) separately.If you need to change in logic you do not have to worry about presentation(View).
Regards,
Albert

What are the advantages of using LabVIEW projects in TestStand, as apposed to just a path to a vi

What are the advantages of using LabVIEW projects in TestStand, as apposed to just a path to a vi ?
I am modifying an existing workspace for a new product, and it seems like more work to add the vi's into a LabVIEW project
does it gain anything in the long run

Hi Rusty,
I wanted to quickly clarify on the integration between TestStand and LabVIEW Projects.
As Jeff mentioned, some of the big benefits of using LabVIEW Projects is to organize code and to namespace them.
For instance if you had a project called "Power Supply" that housed all your power supply code and had a VI in that called "Initialize", and another project called "Temperature Chamber" that also had a VI called "Initialize", both these VIs are namespaced by the project, so there is no longer confusion about which "Initialize" VI is being used.
Now from a TestStand point of view, in prior version of TestStand, we lost some of this benefit because TestStand did not know about TestStand projects and called VIs simply as un-namespaced VIs. However, in TestStand 2010 (released last year, free eval available at ni.com/teststand), we added the ability to (optionally) call VIs within the context of their projects. This means that:
VIs are now namespaced by their project, even when called from TestStand
VIs can use project specific constructs like NI-DAQmx tasks and conditional compilation settings
Note: When creating deployments, the VIs maintain their projects and namespacing, so this benefit holds true for deployments as well.
Additionally, someone had mentioned looking into using lvlibs to namespace your VIs for deployment. Two comments:
With TestStand 2010, this is no longer neccessary since the project itself namespaces the VIs
You might also want to look into LabVIEW Packed Project Libraries, which combined several VIs into a single file. Think of it as a DLL specific to LabVIEW that is as easy to call as normal LabVIEW VIs. TestStand 2010 can call VIs that are exposed by PPLs. In addition, the deployment utility can automatically pack your VIs into PPLs for deployment.
Hope this is helpful!
Jervin Justin
NI TestStand Product Manager

What are the advantages and disadvantages of suppressed and unsuppressed content in indesign layer option?

what are the advantages and disadvantages of suppressed and unsuppressed content in indesign layer option?

I occasionally use layers set to suppress output for holding text that differs from the text in the visible part of a document that I need for variables or TOC entries sometimes, or for notes or guides I want in the file but I don't want printed. You might also want to suppress a layer with some sort of overlay, like the die-lines for a die-cut piece, when you export a PDF for screen viewing.
I'm sure you can come up with other reasons for having content on a page in the layout, but not in the final output.

What are the advantages and disadvantages of the Joint operation

Hi, I am currently trying what out the advantages and disadvantages of the Joint Operation ... any help would be appreciated

The advantage of join operations are that joins allow
retrieval or data from more than one table at a
time.
A disadvantage of join operations is that the SQL
statement may be more complicated to write and read
than multiple simple selects.
Another advantage is that fetching data from multiple
tables in a single SQL statement is that using a join
is likely to be more efficient than using several
simple SQL statements with procedural logic
performing the work of the join.
There are basic three types of join operations in
Oracle: nested loop, hash join, and sort/merge.
You can find descriptions of these operations in the
Oracle Performance and Tuning manual.
HTH -- Mark D Powell --
Thanks for the information Mark ... Much Appreciated

Converting RAW to DNG! What are the advantages / disadvantages?

I have Canon cameras and shoot RAW, but the question itself is surely also valid for Nikon, Sony or other brand-shooters.
When importing my pictures to Lightroom, I could convert them to DNG but didn't do this up to now, because I do not know what I loose. I suppose that I loose the ability to process my files with DPP, but I will not do that anyhow. I can appreciate the advantage of having the file in an open documented format, where even I could easily write a reader for it. So the answer should not be what I can easily find in the Adobe introduction into DNG. I have also the DNG specification in front of me, and I can read it, because I once wrote a program to read TIFF files. I understand that I could add the original RAW image stream, but I do not want using up the space wasted for this. I know, that all development parameters used for the specific RAW image can be written with the image file instead of having those stored in a database or a side-car-file.
But what I did not find until now a technical explanation about what happens during the convert. Who can enlighten me? Where do I find the missing technical explanations?
Thanks in advance!
Lucien.

Feierwoon wrote:
That wasn't the question... .
Based on the title of the thread and your initial post, it seems like your question had a lot of
"What are the advantages / disadvantages?"
in it, and only a little
"What happens at a technical level when converting"
But if you want more detailed info about conversion, and you have the aptitude to understand, I recommend doing what Lr5user-pt recommended:
Download the DNG SDK and dig in - all your questions will be answered (and if not, you can also ask DNG-specific technical questions in the DNG forum).
As far as my "sources" regarding the technical summary I presented, they are many and varied, none of which are the DNG SDK. In other words, my knowledge is based more on experience over the years - I don't know all the details under the hood..
Some experiments to consider doing:
* exiftool (-X) a proprietary raw file, then convert to DNG and repeat.
* open a proprietary raw in a DNG-supporting software of your choice and inspect metadata, then open the converted DNG in the same software and re-evaluate. Compare to proprietary raw opened in manufacturer's software, and what you see via exiftool.
Tom Hogarty (Lightroom project manager) and others who know have said: "DNG converter discards no metadata", and I believe them, but haven't verified for myself. Yet once proprietary metadata is in the DNG, most (all?) software will no longer decode it. A prime example is focus points - presumably they're there, but once converted, focus point feature is no longer supported. The amount of work required to support converted focus point data is unknown (to me), but as far as I know, no software has ventured to do it. If you want focus points, don't convert.
If you want the truth, I think for most people it's "not wise" to convert to DNG. Why? because unless you already know why you are converting (and need to convert to satisfy your goals), or you already know why you must NOT convert (e.g. so you can open the files in mfr.software, and see focus points..) the pros and cons are likely to be a wash, and now you have twice the number of raw files, unless you discard your originals, which would be REALLY "not wise", in my opinion. If you find the notion of "openly documented format" sufficiently compelling, then, ya know, more power to ya (I don't judge..), but there is no guarantee that DNG will outlast NEF (or..), and if it does, there will be ample opportunity to convert before you're left in the cold, unless you're stuck in a cave for a few decades, or are kryogenically frozen.. True, if all companies die, you may be able to write your own DNG converter (/reader), given the DNG documentation, but FWIW, NEF is also thoroughly documented (document is in freely downloadable SDK), and reverse engineerable (that's what Adobe and Phil Harvey does), so you could also write your own NEF converter, so not really a very compelling argument, not this year anyway - ask me again in a few decades..
If filesize is a main draw, then be sure NOT to save the hi-rez previews in your DNGs, otherwise you've just lost most or all of the filesize advantage. Also, you can strip previews from some proprietary raws (e.g. NEFs), to reduce filesize.
Personally, if DNG supported sidecars, I would be more likely to convert, because file-management/backup is only an issue if you "forget" about xmp sidecars (and I do not forget), and I'd rather have my xmp in separate ready-to-read xml text files, rather than embedded in binary files, but hey, that's me..
PS - I always use/encourage-others-to-use DNG when distributing raws to others for use in Adobe software, so xmp is not separate and can not get lost.
PPS - proprietary raws and dngs are both just glorified tiff files - raw data, previews, and metadata..
Don't get me wrong: I am NOT anti-DNG, and in fact - just the opposite: I am PRO dng, it's just that I wouldn't (don't) convert my own raws to DNG at this point. If you find the reasons to convert now are sufficiently compelling, you have my complete support and cooperation, fwiw..
Cheers,
Rob

Hello Anybody, I have a question. Can any of you please suggest me how to make an xml file from the database table with all the rows? Note:- I am having the XSD Schema file and the resulted XML file should be in that XSD format only.

Hello Anybody, I have a question. Can any of you please suggest me how to make an xml file from the database table with all the records?
Note:- I am having the XSD Schema file and the resulted XML file should be in that XSD format only.

The Oracle documentation has a good overview of the options available
Generating XML Data from the Database
Without knowing your version, I just picked 11.2, so you made need to look for that chapter in the documentation for your version to find applicable information.
You can also find some information in XML DB FAQ

What are the advantages of compressor and it it even necessary

what are the advantages of compressor and it it even necessary?

Necessary for some and not for others – probably a large majority – who can by with the presets avalaible in FCX.
The users who need Compressor are those who want to control the parameters of the encodes to get the best possible trade-off between file size and quality. Or those who want to do things like standards conversions, complex frame speed changes, better re-scaling capabilities, de-interlacing, re-interlacing, output formats beyond which are available in FCX, chapter markers for DVD and Blu-Ray authoring, batch conversions for multiple purposes through droplets, access to clusters for faster rendering.
Russ

What is VIEW in Database table what is the advantage

Similar Messages

Maybe you are looking for