Object-oriented APEX. Best practices.

Hello,
in my company we are developing quite big application in Apex. At the beginning we saw Apex as a very developer friendly application, but now we have problem with it.
Our application has about 100 pages, most of them are not only reports but are also designed to edit and add new data. We are often using javascript and plsql procedures to handle collections and error processing. There are a lot of elements that are identical on several pages – not only processes, but also buttons, branches etc. – and when something changes, we must do the same operation on every page. Do you know any way to deal with it in better way?
Are there any “best practices” for APEX to make it more object-oriented? I know I can put e.g. plsql procedures as a function in database, but what about button functions etc.? Maybe I should name most important buttons in the same way and handle them using javascript?
Regards,
Przemek Staniszewski

Hi Przemek,
I'm not an object oriented expert so I probably can't offer you too much in the way of advice here, I'm old school from relational theory, 3GL etc. But one of the things to remember is that Apex isn't one single language like Java where it is easier to maintain good object oriented practicies and even enforces and encourages. Apex is a collection of technologies such as Relational Design, SQL, PL/SQL, HTML and Javascript which are all held together by a declarative programming interface.
Although all these technologies have varying degrees of object orientism, they are all quite distinct technologies which work together well but don't really help each other in maintaining or enforcing OO good practices. I think it would be hard to reverse engineer an existing application, but with some thought, kowledge and advice from the right areas you should be able to put together some good design and coding standards which will serve you well going forward.
There are some documents and threads you should be able to find which will also help you, but also remember you are also dealing with some long established technologies such as Relation Database Design and SQL. Too often developers with skills in more recent languages get lost in the API front end and assume the database isn't really part of the application. You know, DBA stuff. For my money the database is the centre and the most important part of the application.
My two cents worth anyway.
Andre

Similar Messages

APEX best practices?

Hi,
I am a newbie to the Oracle world and am considering undertaking a pilot project based around OracleXE/APEX to evaluate Oracle technology for a customer. The only way this makes sense (as opposed to say PHP/PostgreSQL) is if the productivity and maintenance gains from using APEX are tangible. However I am a little dismayed at how fragile the technology seems to be for real world software engineering.
The main areas of concern at the moment are
version control for software changes, How do I save development snapshots automatically using git or svn or something similar
documentation and structuring guidelines, how do I document a system to make it easy for someone else to maintain it?
debugging/development guidelines, what are good debugging/tracing techniques?
undo, how can I recover from e,g. accidental deletion of parts of an APEX application?
Are there best practice guides out there?, Oracle documentation is copious and well written but seems (to me) ominously silent on topics like these.
If there is a TFM out there, more than happy enough to 'R' it.

version control for software changes, How do I save development snapshots automatically using git or svn or something similarThere's an command-line export utility that ships with APEX.
documentation and structuring guidelines, how do I document a system to make it easy for someone else to maintain it?I believe there's a self-documenting function, can't remember where though
debugging/development guidelines, what are good debugging/tracing techniques?Search the APEX Users Manual. You can put a page in debug mode, trace sessions by appending &p_trace=YES to the URL, and remote debug with SQL Developer.
undo, how can I recover from e,g. accidental deletion of parts of an APEX application?Make sure you set the undo_retention parameter to something longer than 15 minutes. You can then export pages / application "as of" 60 minutes ago (or whatever time your flashback setting supports), then re-import that component. More details here:
http://tylermuth.wordpress.com/2007/11/17/apex-flashback-sql-developer-undo/
Are there best practice guides out there?, Oracle documentation is copious and well written but seems (to me) ominously silent on topics like these.If you look on the APEX page on otn (otn.oracle.com/apex), there are a bunch of tutorials if you prefer that style over plain old doc.
If there is a TFM out there, more than happy enough to 'R' it.There's also a great book on APEX that's obviously in a different writing style:
http://www.amazon.com/Oracle-Application-Express-Experts-Voice/dp/159059827X
One additional topic, and IMHO the most import topic: "Community". APEX has a HUGE community, mainly focused in this forum. People are very willing to help, and with apex.oracle.com, you can even have people look at your app and debug it for you. Some of the top posters on this forum are either current or former members of the Development Team or make their living as APEX consultants.
Good luck,
Tyler

Syncing App IDs across servers -- Best Practice?

This is prompted by a comment chrisstephens made in the thread at non-existent applications in non-existent workspaces reserving app id's
Our developers are convinced that the application id's between our dev + staging
+ production environments need to be synchronized.Our team also keeps our dev, test, and prod server app IDs synchronized -- for instance, the Widget Reporting App is always app # 38 on all three servers. For us, it's not something we see as REQUIRED, but it is convenient, and a general sanity check. If the numbers didn't sync, it seems it would be all too easy to get values mixed up and accidentally field an app to the wrong place (possibly overwriting some other application).
What is the community's opinions on this? Would you consider this an Apex Best Practice? Just a habit for some groups? Or overly rigid thinking?
(I personally fall in the Best Practice group.)

One good reason to keep them the same is so that there are no differences between what is tested in one environment and what is deployed in another. Case in point, just last week someone demonstrated that an application's authentication scheme failed when the application ID was changed from xxx to xxxxxxxxx (a longer string of digits). Of course this was due to a previously unknown bug, but that's what testing should reveal.
Another good reason is to make it possible to export application components (pages, etc.) from one database (say, dev) and install them into an application in another database (say, prod). This is not possible if the application IDs are different.
Scott

Best practice when developing APEX apps and using a SVN repository

Hi experts,
I wanted to get your opinion on best practice regarding how to use SVN and APEX combined.
The idea is basically how to structure and how to save APEX apps the best way in a repository.
I am currently working with a custom SVN structure, not using the default TRUNC/TAGS one : every app has a folder , under every app folder i have PAge number folders, and for each page reports, regions and global objects separated.
This helps me because its more readable then saving the whole page export, its good for small changes and i have a clear overview of every bit and piece.
What is everybody else using or is there a best practice to follow here that i dont know?
Kind regards,
Alex

@tomaugerdotcom
Something like this might help: https://testflightapp.com/
Concevably, you could roll your own internal service if that particular one doesn't suit you. (I don't have any knowledge about how they are doing it, but it shouldn't be hard to figure out since Apple's constraining rules would only allow a few possibilities.)
USB app install and debugging isn't supported on iOS. You have to use wireless.
Another option specifically for multi-touch dev/testing, is to use an Android device.

Integrating APEX and E-Business best practices?

My company has been using the E-Business Suite for the past decade, and I've finally convinced them to set up APEX (now that 4.0 is out). However, I haven't been able to find much that's current on integrating the two, other than [this paper|http://www.oracle.com/technology/products/database/application_express/pdf/apex_ebs_wp_cabot_consulting.pdf] by Cabot Consulting. Is this the accepted best practice for integrating the two systems?
Our DBA is hesitant about letting us use the apps schema as the parsing schema (per the document's recommendation), as that gives APEX developers almost unlimited access ("the keys to the kingdom", in his words). Is there a better way, or something I can tell him to allay his concerns?
Thanks,
-David

Hi David,
You don't have to use APPS as the parsing schema, you can use another schema and grant execute on an EBS authenticate function that you have created in the APPS schema. This will work fine. You will also have to grant access to any other APPS objects that you need to use.
Apart from the bit of extra work of granting the required privileges the downside of not using the APPS schema as the parsing schema is that not all the EBS APIs will work if run from another schema, most will but some won't because they use dynamic SQL which expects the parsing schema to be APPS.
This is the reason why most EBS developers do all their work in the APPS schema e.g. when developing conc request programs. Which ever approach you take you need to ensure that APEX is clamped down in production with no developer access.
So it all depends on what you are hoping to achieve and how you design your APEX applications. If you not calling EBS APIs you will be fine with a separate schema.
Similarily with the performance, you may be fine on the same server, for example, if you have a separate RAC node for Apex or are using separate tables/indexes. On the other had if you are try to use the APPS security views for reporting in APEX you will quickly run into performance issues.
Rod West

Best Practice question - null or empty object?

Given a collection of objects where each object in the collection is an aggregation, is it better to leave references in the object as null or to instantiate an empty object? Now I'll clarify this a bit more.....
I have an object, MyCollection, that extends Collection and implements Serializable(work requirement). MyCollection is sent as a return from an EJB search method. The search method looks up data in a database and creates MyItem objects for each row in the database. If there are 10 rows, MyCollection would contain 10 MyItem objects (references, of course).
MyItem has three attributes:
public class MyItem implements Serializable {
    String name;
    String description;
    MyItemDetail detail;
}When creating MyItem, let's say that this item didn't have any details so there is no reason to create MyitemDetail. Is it better to leave detail as a null reference or should a MyItemdetail object be created? I know this sounds like a specific app requirement, but I'm looking for a best practice - what most people do in this case. There are reasons for both approaches. Obviously, a bunch of empty objects going over RMI is a strain on resources whereas a bunch of null references is not. But on the receiving end, you have to account for the MyItemDetail reference to be null or not - is this a hassle or not?
I looked for this at [url http://www.javapractices.com]Java Practices but found nothing.

I know this sounds like a specific apprequirement,
, but I'm looking for a best practice - what most
people do in this case. It depends but in general I use null.Stupid.Thanks for that insightful comment.
>
I do a lot of database work though. And for that
null means something specific.Sure, return null if you have a context where null
means something. Like for example that you got no
result at all. But as I said before its's best to
keep the nulls at the perimeter of your design. Don't
let nulls slip through.As I said, I do a lot of database work. And it does mean something specific. Thus (in conclusion) that means that, in "general", I use null most of the time.
Exactly what part of that didn't you follow?
And exactly what sort of value do you use for a Date when it is undefined? What non-null value do you use such that your users do not have to write exactly the same code that they would to check for null anyways?

Best practice - caching objects

What is the best practice when many transactions requires a persistent
object that does not change?
For example, in a ASP model supporting many organizations, organization is
required for many persistent objects in the model. I would rather look the
organization object up once and keep it around.
It is my understanding that once the persistence manager is closed the
organization can no longer be part of new transactions with other
persistence managers. Aside from looking it up for every transaction, is
there a better solution?
Thanks in advance
Gary

problem with using object id fields instead of PC object references in your
object model is that it makes your object model less useful and intuitive.
Taking to the extreme (replacing all object references with their IDs) you
will end up with object like a row in JDBC dataset. Plus if you use PM per
HTTP request it will not do you any good since organization data won't be in
PM anyway so it might even be slower (no optimization such as Kodo batch
loads)
So we do not do it.
What you can do:
1. Do nothing special just use JVM level or distributed cache provided by
Kodo. You will not need to access database to get your organization data but
object creation cost in each PM is still there (do not forget this cache we
are talking about is state cache not PC object cache) - good because
transparent
2. Designate a single application wide PM for all your read-only big
things - lookup screens etc. Use PM per request for the rest. Not
transparent - affects your application design
3. If large portion of your system is read-only use is PM pooling. We did it
pretty successfully. The requirement is to be able to recognize all PCs
which are updateable and evict/makeTransient those when PM is returned to
the pool (Kodo has a nice extension in PersistenceManagerImpl for removing
all managed object of a certain class) so you do not have stale data in your
PM. You can use Apache Commons Pool to do the pooling and make sure your PM
is able to shrink. It is transparent and increase performance considerably
One approach we use
"Gary" <[email protected]> wrote in message
news:[email protected]...
>
What is the best practice when many transactions requires a persistent
object that does not change?
For example, in a ASP model supporting many organizations, organization is
required for many persistent objects in the model. I would rather look the
organization object up once and keep it around.
It is my understanding that once the persistence manager is closed the
organization can no longer be part of new transactions with other
persistence managers. Aside from looking it up for every transaction, is
there a better solution?
Thanks in advance
Gary

Best-practice for use of object styles to manage image text wrap issues when aiming at both print and EPUB output?

I have a work-flow question about object styles, text-wrap, and preparing a long document with lots of images for dual print/EPUB output in InDesign CC 2014.
I am sort of experienced with InDesign but new to EPUB export. I have hundreds of pages and hundreds of images so I'd like to make my EPUB learning curve, in particular, less painful.
Let me talk you through what I'm planning and you tell me if it's stupid.
It's kind of a storybook-look I'm going for. Single column of text (6" by 9" page) with lots of small-to-medium images on the page (one or two images per page), and the text flowing around, sometimes right, sometimes left. Sometimes around the bounding box, sometimes following the edges of the images. So in each case I'm looking to tweak image size and placement and wrap settings so that the image is as close to the relevant text as possible and the layout isn't all wonky. Lovely print page the goal. Lots of fussy trade-offs and deciding what looks best. Inevitably, this will entail local overrides of paragraph styles. So what I want to do, I guess, is get the images as closely placed as possible, before I do any of that overriding. Then I divide my production line.
1) I set aside the uniformly-styled doc for later EPUB export. (This is wise, right? Start for EPUB export with a doc with pristine styles?)
2) With the EPUB-bound version set aside, I finish preparing the print side, making all my little tweaks. So many pages, so many images. So many little nudges. If I go back and nudge something at the beginning everything shifts a little. It's broken up into lots of separate stories, but still ... there is no way to make this non-tedious. But what is best practice? I'm basically just doing it by hand, eyeballing it and dropping an inline anchor to some close bit of text in case of some storm, i.e. if there's a major text change my image will still be almost where it belongs. Try to get the early bits right so that I don't have to go back and change them and then mess up stuff later. Object styles don't really help me with that. Do they? I haven't found a good use for them at this stage (Obviously if I had to draw a pink line around each image, or whatever, I'd use object styles for that.)
Now let me shift back to EPUB. Clearly I need object styles to prepare for export. I'm planning to make a left float style and a right float style and a couple of others for other cases. And I'm basically going to go through the whole doc selecting each image and styling it in whatever way seems likeliest. At this point I will change the inline anchors to above line or custom, since I'm told EPUB doesn't like the inline ones.
I guess maybe it comes down to this. I realize I have to use object styles for images for EPUB, but for print, manual placement - to make it look just right - and an inline anchor seems best? I sort of feel like if I'm going to bother to use object styles for EPUB I should also use them for print, but maybe that's just not necessary? It feels inefficient to make so many inline anchors and then trade them for a custom thing just for EPUB. But two different outputs means two different workflows. Sometimes you just have to do it twice.
Does this make sense? What am I missing, before I waste dozens of hours doing it wrong?

I've moved your question to the InDesign EPUB forum for best results.

Best practice "changing several related objects via BDT" (Business Data Toolset) / Mehrere verbundene Objekte per BDT ändern

Hallo,
I want to start a
discussion, to find a best practice method to change several related master
data objects via BDT. At the moment we are faced with miscellaneous requirements,
where we have a master data object which uses BDT framework for maintenance (in
our case an insured objects). While changing or creating the insured objects a
several related objects e.g. Business Partner should also be changed or
created. So am searching for a best practices approach how to implement such a
solution.
One Idea was to so call a
report via SUBMIT AND RETURN in Event DSAVC or DSAVE. Unfortunately this implementation
method has only poor options to handle errors. Second it is also hard to keep LUW
together.
Another idea is to call an additional
BDT instance in the DCHCK-event via FM BDT_INSTANCE_SELECT and the parameters
iv_xpush_classic = ‘X’ and iv_xpop_classic = ‘X’. At this time we didn’t get
this solution working correctly, because there is always something missing
(e.g. global memory is not transferred correctly between the two BDT instances).
So hopefully you can report
about your implementations to find a best practice approach for facing such
requirements.
Hallo
ich möchte an der Stelle eine Diskussion starten um einen Best Practice
Ansatz zu finden, der eine BDT Implementierung/Erweiterung beschreibt, bei der
verschiedene abhängige BDT-Objekte geändert werden. Momentan treffen bei uns
mehrere Anforderungen an, bei deinen Änderungen eines BDT Objektes an ein
anderes BDT Objekte vererbt werden sollen. Sprich es sollen weitere Objekte geänderte
werden, wenn ein Objekt (in unserem Fall ein Versicherungsvertrag) angelegt
oder geändert wird (zum Beispiel ein Geschäftspartner)
Die erste unserer Ideen war es, im Zeitpunkt DSAVC oder DSAVE einen
Report per SUBMIT AND RETURN aufzurufen. Dieser sollte dann die abhängigen Änderungen
durchführen. Allerdings gibt es hier Probleme mit der Fehlerbehandlung, da
diese asynchrone stattfinden muss. Weiterhin ist es auch schwer die Konsistenz der
LUW zu garantieren.
Ein anderer Ansatz den wir verfolgt hatten, war im Zeitpunkt
DCHCK per FuBA BDT_INSTANCE_SELECT und den Parameter iv_xpush_classic = ‘X’ and
iv_xpop_classic = ‘X’ eine neue BDT Instanz zu erzeugen. Leider konnten wir diese
Lösung nicht endgültig zum Laufen bekommen, da es immer Probleme beim
Übertragen der globalen Speicher der einzelnen BDT Instanzen gab.
Ich hoffe Ihr könnt hier eure Implementierungen kurz beschreiben, dass wir
eine Best Practice Ansatz für das Thema finden können
BR/VG
Dominik

OBIEE Best Practice Data Model/Repository Design for Objectives/Targets

Hello World!
We are faced with a design question that has become somewhat difficult and we need some help. We want to be able to compare side-by-side actual measures with their corresponding objectives/targets. Sounds simple. But, our objectives are static (not able to be aggregated) with multi-dimensionality and multi-levels. We need some best practice tips on how to design our data model and repository properly so that we can see the objective/target for a measure regardless of the dimensions that are used in the criteria and regardless of the level.
Here is some more details:
Example of existing objective table.
Dimension1
Dimension2
Dimension3
Obj1
Obj2
Quarter
NULL
NULL
NULL
.99
1.8
1Q13
DIM1VAL1
NULL
NULL
.99
2.4
1Q13
DIM1VAL1
DIM2VAL1
NULL
.98
2.41
1Q13
DIM1VAL1
DIM2VAL1
DIM3VAL1
.97
2.3
1Q13
DIM1VAL1
NULL
DIM3VAL1
.96
1.9
1Q13
NULL
DIM2VAL1
NULL
.97
2.2
1Q13
NULL
DIM2VAL1
DIM3VAL1
.95
2.0
1Q13
NULL
NULL
DIM3VAL1
.94
3.1
1Q13
- Right now we have quarterly objectives set using 3 different dimensions. So, if an author were to add one or more (or zero) dimensions to their criteria for a given measure they could get back a different objective. They could add Dimension1 and get 99%. They could add Dimension1 and Dimension2 and get 98%. They could add all three dimensions and get 97%. They could add zero dimensions (highest grain) and get 99%. Using our existing structure if we were to add a new dimension to the mix the possible combinations would grow dramatically. (Not flexible)
- We would like our final solution to be flexible enough so that we could view objectives with altogether different dimensions and possibly get different objectives.
- We currently have 3 fact tables with 3+ conformed dimension tables and a few unique dimension tables.
Could anyone share a similar situation where you have implemented a data model structure with the proper repository joins to handle showing side-by-side objectives/targets where the objectives were static and could be displayed at differing levels with flexible dimensions as described?
Any help would be greatly appreciated.

hi..yes this suggestion is nice...first configure the sensors(activity or variable) ..then configure the sensor action as a JMS Topic which will in turn insert the data into a DB..Or when u configure the sensor action as a DB..then the data goes to Oracle Reports schema..if there is any chance of altering the DB..i mean if there is any chance by changing config files so that the data doesnt go to that Reports schema and goes to a custom schema created by any User....i dont know if it can b done...my problem is wen i m configuring the jms Topic for sensor actions..i see blank data coming..for sm reason or the other the data is not getting posted ...i have used a esb ..a routing service based on the schema which i am monitoring...can any1 help?

Best Practice Question - Business Logic in Value Objects?

Just wondering what people's thoughts on best practices for setting properties of Value Objects.
For instance, I have several getter/setters in one of my Value Objects with logic in the setter that uses the value to set values of other properties.
For example, I have a Value Object that has the following properties:
category (of type Category, which is another Value Object with properties "name" and "id")
categoryId (of type int)
categoryUpdated (of type Boolean)
I have a collection of Category Objects in the Model. When I set the categoryId of this class, I set the "categoryUpdated" to true, and dispatch an CairngormEvent to that find the "category" with the specified "categoryId" and set the "category" property to this item.
So what is the best practice? To simply make the "categoryId" a public variable, and create a new Event/Command to perform all this logic? Or is it ok to do it all in the Value Object setter?
Thanks.

Hi Eric,
I can't speak for best practices, but the only logic I've ever added to a VO were getters: an example was a set of getters on an airline flight VO to get overall flight departure/arrival times/cities from an array of flight segments in a property of the VO.
I feel uneasy (in the nicest possible way) about your VO for two reasons: firstly it has a strong dependency on bits of the Cairngorm framework to look up the category (and VOs normally don't need to depend on anything), and secondly the intent of Commands in Cairngorm is more to represent user gestures than to wire up VO properties (I often see people shoehorning stuff into Commands that might be better of as plain old business utility classes). I would rather see an UpdateCategoryCommand (that's what the user is trying to do?) that updates categoryId and hits a delegate to populate the category property.
That said you might have a very good reason for doing this. Could you tell us where the code is that's setting categoryId, and if anything is using categoryUpdated?
Cheers,
Robin

Best practice for linking fields from multiple entity objects

I am currently transitioning from PHP to ADF. I'm looking for the best practice for linking data from multiple entity objects.
Example:
EO 'REQUESTS' has fields: req_id, name, dt, his_stat_id, her_stat_id
EO 'STATUSES' has fields: stat_id, short_txt_descr
'REQUESTS' is linked to EO 'STATUSES' on: STATUSES.stat_id = REQUESTS.his_status_id
'REQUESTS' is also linked to EO 'STATUSES' on: STATUSES.stat_id = REQUESTS.her_status_id
REQUESTS.his_status_id is independent of REQUESTS.her_status_id
When I create a VO for REQUESTS, I want to display: REQUESTS.name, REQUESTS.dt, STATUSES.short_txt_descr (for his_stat_id), STATUS.short_txt_descr (for her_stat_id)
What is the best practice for accomplishing this? It appears I could do it a few different ways:
1. Create the REQUESTS VO with a LOV for his_stat_id and her_stat_id
2. Create the REQUESTS VO with the join to STATUSES performed within the query for the VO. This would require joining on the STATUSES EO twice (his_stat_id, her_stat_id)
3. I just started reading about View Links - would that somehow do what I'm looking for?
I also need to be able to update his_status_id and her_status_id through the by selecting a STATUSES.short_txt_descr from a dropdown.
Any suggestions on how to approach such a stupidly simple task?
Using jDeveloper 11.1.2.2.0 if that makes a difference in the solution.
Thanks ahead of time,
CJ

CJ,
I vote for solution 1 as it's just your use case. As you said you what to update the his_status_id and her_status_id through the by selecting a STATUSES.short_txt_descr by a drop down. This is exactly the LOV solution.
ViewLinks are used fro master detail navigation (which you don't do here) and Joining the data make it difficult to update (and you still need a LOV for the drop down box.
Timo

Best practice for number of result objects in webi

Hello all,
I am just wondering if SAP has any recommendation or best practice document regarding number of fields in Result Objects area for webi. We are currently running on XI 3.1 SP3...one of the end user is running a webi with close to 20 objects/dimensions and 2 measure in result objects. The report is running for 45-60 mins and sometimes timing out. The cube which stores data has around 250K records and the report would return pretty much all the records from the cube.
Any recommendations/ best practices?
On similar issue - our production system is around 250GB what would be the memory on your server typically...currently we have 8GB memory on the sap instance server.
Thanks in advance.

Hi,
You mention Cubes so i suspect BW or MS AS . Yes, OLAP data access (ODA) to OLAP DataSets is a struggle for WebIntelligence which is best at consuming Relational RowSets.
Inefficient MDX queries can easily be generated by the webi tool, primeraly due to substandard (or excessive) query and document design. Mandatory filters and focused navigation (i.e. targetted BI questions) are the best for success.
Here's an intersting article about "when is a webi doc too big" https://weblogs.sdn.sap.com/pub/wlg/18706
Here's a best practice doc about webi report design and tuning ontop of BW MDX : https://service.sap.com/~sapidb/011000358700000750762010E
Optimization of the cube itself, including aggregates and cache warming is important. But especially use of Suppress Unassigned nodes in the BW hierarchy, and "query stripping" in the webi document.
finally, patch level of the BW (BW-BEX-OT-MDX) component is critical. i.e. anything lower than 7.01 SP09 is trouble. (memory management, mdx optimization, functional correctness)
Regards,
H

Best practice for initializing objects in a JSF backing bean?

Hi,
What is the best practice for initializing some objects in the JSF to-page backing bean before the to-page is displayed for the first time? The initialization would vary and depend upon a command link in the from-page.
Regards,
Al Malin

f:view has two new attributes in 1.2: beforePhase and afterPhase
which allows you to specify a phase listener method
which will be called before and after the view is processed.

Is there any best practice or standard for database object naming ?

Hi
Thank you for reading my post
is there any standard or best practice for databse objects naming ?
for example how should we name columns of a table ? should it be like TOTAL_VOTE or TOTALVOTE and many other items.
Thanks

what does oracle suggest as a naming schema for tables , fields , views. indexes , tablespaces , ... If you look at the data dictionary you will see that not even Oracle keeps rigidly to any specific standard, although there are tendencies :)
"The nice thing about standards is that there are so many of them to choose from."
-- Andrew Tannenbaum
Cheers, APC

Object-oriented APEX. Best practices.

Similar Messages

Maybe you are looking for