ObjectId on persistent object
Hello
Using Datastore identity, Is it possible to declare an instance variable on
a persistent object which will "automatically" be populated with the
datastore objectid when the enclosing object is retrieved from persistence?
This would be in preference to always calling JDOHelper.getObjectId(obj)?
[or persistenceManager.getObjectId(obj) ]
Thanks
..droo.
We've done this using the jdoPostLoad callback as follows:
public void jdoPostLoad()
setObjectID(JDOHelper.getObjectId(this).toString());
Scott
Drew Lethbridge wrote:
Hello
Using Datastore identity, Is it possible to declare an instance variable on
a persistent object which will "automatically" be populated with the
datastore objectid when the enclosing object is retrieved from persistence?
This would be in preference to always calling JDOHelper.getObjectId(obj)?
[or persistenceManager.getObjectId(obj) ]
Thanks
..droo.
Similar Messages
-
How can i get the unitOfWork or the persisting object in to my listener???.
hi,
i have a listener class which extends SessionEventAdapter ....as shown below
public class MyLister extends SessionEventAdapter{
public void postCommitUnitOfWork(SessionEvent event) {
System.out.println("POST COMMIT OF WORK");
// How can i get the unitOfWork or the persisting object in to my listener???
Another class makes use of this listener by adding the listener into a getEventManager() of a session ....
public final class AetbProcessStatusClient {
public static final void main(String[] args)
{ Project project =
XMLProjectReader.read("META- INF/AetbProcessStatus.xml",
Thread.currentThread().getContextClassLoader());
DatabaseSession session = project.createDatabaseSession();
MyLister myListener = new MyLister();
session.getEventManager().addListener(myListener);
session.login();
UnitOfWork uow = session.acquireUnitOfWork();
uow = session.acquireUnitOfWork();
Vector vec =
(Vector)uow.executeQuery("SQFunctionIdProcessStatus", AetbProcessStatus.class);
AetbProcessStatus processStatus = new AetbProcessStatus();
processStatus = (AetbProcessStatus)vec.get(0);
processStatus.setRunStat('E');
processStatus.setProgramSeqNo(10);
uow.commit();
now my question --> How can i get the unitOfWork or the persisting object in to my listener???....
ie the object "processStatus" into my listenerThe SessionEvent's session (getSession()), should be the UnitOfWork. You can access the UnitOfWork or UnitOfWorkImpl methods to access the objects in the unit of work. getUnitOfWorkChangeSet() will return the changes made in the UnitOfWork.
-- James : http://www.eclipselink.org -
Switch between transient and persistent objects?
Hi Folks,
I'm Re: transient object to persistent to ask this type of question, but couldn't find an answer.
Using persistent classes, does anyone know an elegant way to convert a transient object to a persistent one and vice versa? There is no standard functionality provided that I can see, and cloning the object results in clashing keys.
What am I trying to accomplish?
I need an object instance which <i>may</i> exist in the DB and if not, it <i>may</i> need to be saved for future use. I'm using a table with key fields K1 and K2 and the app will ask for an object instance using the full key K1+K2.
If the object doesn't find a DB record for K1K2 then it should instantiate itself with values for K1blank. Here is where I'm considering transient in order to provide the app with default functionality defined in record K1+blank.
If a write access occurs to a transient object then is should become persistent and the K1+K2 record be created.
Any ideas appreciated.
Cheers,
MikeHi Mike,
I written something similar working on Persistent Objects.
The only point of attention is that you cannot create a new persistent while a transient is resident in memory.
This is checked by the OS system during the creation of a new persistent:
in method CREATE_PERSISTENT of Basis Class, there is a check on the existing object:
* Precondition : No object exists with the given business key, neither
* in memory nor on database.
So, you can create a new transient, fill it with the values you need and then pass this values to the agent to create a new persistent, but only after releasing the existing transient (because they will have the same key).
I've solved the problem like this:
METHOD flush.
"IMPORTING value(im_transient) TYPE REF TO zcl_liquidate_daily_bo
"IMPORTING value(im_commit) TYPE xfeld
"IMPORTING value(im_agent) TYPE REF TO zca_liquidate_daily_bo
"RETURNING value(re_persistent) TYPE REF TO zcl_liquidate_daily_bo
"--> raised by event PERNR_PROCESSED
DATA: s_dip_liq TYPE zhr_tm_dip_liq.
s_dip_liq-zpernr = im_transient->get_employee_no( ).
s_dip_liq-zsocmat = im_transient->get_matricola_legale( ).
s_dip_liq-zdataev = im_transient->get_event_date( ).
s_dip_liq-zcodev = im_transient->get_event_type( ).
s_dip_liq-zdescev = im_transient->get_event_descr( ).
s_dip_liq-zmotev = im_transient->get_event_reasn( ).
s_dip_liq-zmeseall = im_transient->get_mese_allineamento( ).
s_dip_liq-zannoall = im_transient->get_anno_allineamento( ).
* // Invalidate the transient before create the persistent!
im_agent->if_os_factory~release( im_transient ).
CLEAR im_transient.
IF im_commit EQ abap_true.
TRY.
re_persistent =
im_agent->create_persistent( EXPORTING i_anno_allineamento = s_dip_liq-zannoall
i_mese_allineamento = s_dip_liq-zmeseall
i_employee_no = s_dip_liq-zpernr
i_event_date = s_dip_liq-zdataev
i_event_type = s_dip_liq-zcodev
i_event_descr = s_dip_liq-zdescev
i_event_reasn = s_dip_liq-zmotev
i_matricola_legale = s_dip_liq-zsocmat ).
CATCH cx_os_object_existing.
ENDTRY.
COMMIT WORK AND WAIT.
ENDIF.
ENDMETHOD.
This method is called inside a loop on a table that containes references to transient objects.
For each object I perform some tasks, and if all it's ok I raise the event PERNR_PROCESSED, which automatically calls this method FLUSH, transferring the transient to the persistent.
Return Object is the new persistent, which will be passed back to the internal table, changing the content from the transient to the new persistent.
Hope this helps,
Roby. -
Problem with Persistent Object as Reference Attribute of Persistent Object
Hello All,
I have a problem with a persistent class that contains a reference attribute to another persistent class. I can write the reference object attribute to the DB but when I read the reference attribute back from the DB the object is null. Allow me to explain...
I have two tables; one is a data table with one key field of type OS_GUID, the second is a mapping table with several business key fields and two further fields; an instance GUID and a class identifier GUID. The data table is used to contain all the data for an object. The mapping table is used to hold a relationship between the GUID assigned in the data table and the business key. The mapping table has been structured in this way by following the help here:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/df/e785a9e87111d4b2eb0050dadfb92b/frameset.htm
and the field mapping in persistent class for the mapping table has been mapped following the help here:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/06/f23c33638d11d4966d00a0c94260a5/frameset.htm
The code I use to create entries in the data and mapping table is:
<-snip->
DATA:
gv_blank_data_guid TYPE REF TO zcl_ps_data,
gv_data_guid TYPE os_guid,
go_data_ps TYPE REF TO zcl_ps_data,
go_data_agent TYPE REF TO zca_ps_data,
go_data_map_ps TYPE REF TO zcl_ps_data_map,
go_data_map_agent TYPE REF TO zca_ps_data_map,
go_exc TYPE REF TO cx_root.
go_data_agent = zca_ps_data=>agent.
go_data_map_agent = zca_ps_data_map=>agent.
TRY.
Check if there's already data with the business key on the DB
go_data_map_ps = go_data_map_agent->get_persistent(
i_data_ref = iv_data_ref
i_action = iv_action ).
... if there is then exit.
EXIT.
CATCH cx_root INTO go_exc.
ENDTRY.
TRY.
Create the data...
go_data_ps = go_data_agent->create_persistent(
i_root_guid = gv_blank_data_guid
i_req_date = iv_req_date ).
TRY.
... finally, write the new data to the data business key map table
go_data_map_ps = go_data_map_agent->create_persistent(
i_data_ref = iv_data_ref
i_action = iv_action
i_data_guid = go_data_ps ). "note1
CATCH cx_root INTO go_exc.
ENDTRY.
CATCH cx_os_object_not_found.
ENDTRY.
COMMIT WORK.
<-snip->
The fact that it is possible to pass the object GO_DATA_PS in the call to GO_DATA_MAP_AGENT (the line that I've put the comment "note1" on) indicates to me that the reference to the data persistent object can be written to the DB by the mapping persistent object. After executing the above code the mapping table object and class identifier fields are populated. Also, if multiple entries are written to the tables then the class identifier field in the mapping table is always the same and the object ID is different as expected.
However, the problem I have is if I read an object from the DB using the business key with the following code:
<-snip->
DATA:
gv_req_date type datum,
gv_data_guid TYPE os_guid,
go_data_ps TYPE REF TO zcl_ps_data,
go_data_agent TYPE REF TO zca_ps_data,
go_data_map_ps TYPE REF TO zcl_ps_data_map,
go_data_map_agent TYPE REF TO zca_ps_data_map,
go_exc TYPE REF TO cx_root.
go_data_agent = zca_ps_data=>agent.
go_data_map_agent = zca_ps_data_map=>agent.
TRY.
Read data mapping with the business key
go_data_map_ps = go_data_map_agent->get_persistent(
i_data_ref = iv_data_ref
i_action = iv_action ).
... then read the data.
TRY.
CALL METHOD go_data_map_ps->get_data_guid
RECEIVING
result = go_data_ps.
CATCH cx_os_object_not_found.
ENDTRY.
CATCH cx_root INTO go_exc.
ENDTRY.
<-snip->
At no point during this code are the attributes of the object of the persistent class for the data table populated with the contents of the fields of the data table referenced as the attribute of the mapping table. To clarify, when viewing the object in the debugger all the attributes of the mapping object that are simple table fields are populated with the values of the fields of in the mapping table, however, the attributes of the object that represents the persistent class for the data table are not populated with the fields of the data table. I had hoped that by reading the mapping table object the data object would automatically be populated. Is there another step I need to perform to populate the data object?
I'm sorry if the above is hard to follow. Without being able to provide screenshots it's difficult to explain.
If someone has managed to store references to persistent objects in a table and then read the references back could you list the steps you went through to create the persistent classes and include the code that reads the objects please? The code I have almost works, I must be just missing some subtle point...
Thanks in advance,
Steve.Hi Andrea,
The iObject being replicated at item level for Service Complaints is the SAP standard behaviour.
Generally we raise complaint refering to some sales or service issues. In your scenario you are trying to create a complaint based on an iObject, then you have to mention the corresponding product details. I dont see any business requirement not to copy the iObject product at the item level.
If you want it then I think only you have to write a Z program for it.
Hope this helps!
Regards,
Chethan -
Does anyone know if ABAP Persistent Objects support cloning?
I can clone the object using a SYSTEM-CALL (though I'd rather not), however that would still mean breaking the rules to set the object key to a new value.
At the moment the only solution appears to be creating a new persistent or transient object via the agent and manually assigning the attributes.Thanks Uwe. I knew about the SYSTEM-CALL but in this case it does not help.
My problem is that the object key of a persistent object does not appear to be easily modified even from within the object. I want to clone the object and then modify the key to avoid insert collisions.
So far as I can see there is no simple way of modifying the business key of a persistent object.
For now I've implemented IF_OS_CLONE~CLONE in a public method of my persistent object, created a new persistent object and manually assigned the attributes. Unfortunately the code will have to be modified whenever a new attribute is added. -
Equality between primitive and persistent objects
Folks,
I have discovered by chance that the KODO Query implementation allows me
to test for equality between an Integer and a persistent object. This is
actually phenomenally useful because it allows me to easily work around
some really inefficient auto-generated SQL (see below).
I couldn't find anything about this feature in the JDO specs. Is it
accidental? Is it supported, or likely to disappear in future versions?
Dave Syer.
# 'bean' is an object already loaded from the persistence store
javax.jdo.JDOHelper.getObjectId(bean)Bean-101
# it has one mutable property, which is persistence capable
# and also a read-only property which is the database id
# (Integer) of the property:
javax.jdo.JDOHelper.getObjectId(bean.getProperty())Property-371
bean.getPropertyId()371
# get an extent for querying (pm is the PersistenceManager)
ex=pm.getExtent(Bean,0)# First do a query on property...
qu=pm.newQuery(ex);
qu.declareParameters("Property id1");
qu.setFilter("property == id1")# ...generates SQL with additional unnecessary(?) Cartesian join
# to PROPERTY table:
res=qu.execute(bean.getProperty())# resulting SQL:
# SELECT t0.PROPERTY_ID, t0.PROPERTY_ID FROM BEAN t0, PROPERTY t1
# WHERE (t0.PROPERTY_ID = 371 AND t0.PROPERTY_ID =
# t1.PROPERTY_ID)
# Now do a query on propertyId (Integer)...
qu=pm.newQuery(ex);
qu.declareParameters("java.lang.Integer id1");
qu.setFilter("propertyId == id1")# ...but parameter value is allowed to be a Property -- magically
# turned into an integer when the SQL is generated:
res=qu.execute(bean.getProperty())# resulting SQL:
# SELECT t0.PROPERTY_ID, t0.PROPERTY_ID FROM BEAN t0 WHERE
# t0.PROPERTY_ID = 371It is accidental and unsupported.Is there any other way to get round the 'unnecessary join' issue that I
mentioned briefly in my original posting? In a real world example, I was
able to improve performance of a single query by a factor of 100 (and my
DB experts tell me there was no way to optimise indexes or anything at the
RDBMS level and achieve the same result).
DAve. -
Hashtable with persistent object as key and collection as value
I am trying to use a Hastable with a persistent object as the key and a
collection as the value. A long time ago, Abe White said:
"Kodo currently does not support a map in which the keys are persistent
objects and the values are collections. I think your best bet would be
to create an intermediate class that has a 1-1 relation to the "key" and
a collection of persistent objects for the "value". Then keep a
collection of these intermediate objects. You could use jdoPostLoad and
jdoPreStore to hash/unhash the collection of intermediate objects to/from
a Map if you need to."
So I made an intermediate class, which gave me a Hashtable with a persistent
object as the key and another for the value. Then the one for the value
contains the collection. This works but I'm wondering about the
performance, would this method be slower?
Also it was said that version 3.0 would support this. I'm curious if this
is available in 2.5 or if it's still planned for 3.0.
Thanks
MichaelI'm observing massive performance problems but I didn't think it could be
caused by this intermediary object but maybe that is the problem. For
example if I start a transaction to delete everything (with 3,000 records
which in turn has 3,000 records which in turn has 2 lists each) theprogram
crashes before it can finish the transaction. I then put in some loops to
delete 100 records at a time and this runs but it took over an hour to
delete the 3,000 records.
Do you have any other ideas of how to improve the performance? Are there
any alternatives?I solved the performance problem. I was storing web page content (all the
HTML) in a String which by default is in the default-fetch-group. I had
been thinking this was using lazy-loading but it wasn't. So I put
default-fetch-group=false for this property and now the performance is
great. It makes sense because it was retrieving approximately 5k of text
for each record! When deleting 3,000 records this comes out to be 14 megs.
Moral of the story: Use the default-fetch-group wisely!! -
Persistent objects - base table syntax error
I've created a persistent object for a ztable, then the customer has asked me to change the counter field from numc 3 to numc 5, and also remove a field I've done this, and activated and adjusted the table in SE14.
Now, in SE24, I've gone in and adjusted the persistence mapping. When I activate the persistent class, I now get a syntax error in the base class, because it's still referring to components of the old table structure.
When we change the structure of the underlying table, do we have to delete and recreate the persistence classes? Is there a "repair" option?
( It seems it would be useful to have a tool that would generate a basic persistent class directly from a table ).
mattHi Matt,
There is no repair option. As far as I'm aware the persistence class builder function doesn't recognise changes to data types unfortunately. In similar circumstances I've solved the problem by deleting and recreating the class. It's not ideal but at least it's a quick process.
Regards,
Steve. -
Hi,
I'm using objects persistence. I've created a persistent class and using this for storing data in an index cluster table to use the stored data afterwards.
I've created methods for creating persistent object (using export to database), delete object and read object (using import to database).
But i'm not getting how to use update of existing stored object.
Any help would be appreciated.
Regards
RajeshPersistent objects were introduced in ABAP OO in order to replace physical data manipulation via open SQL statements by more abstract OO-typical GET and SET methods for a persistent data object. Has nothing to do with Dequeue/Enqueue.
I recommend reading chapter 3 of [Next Generation ABAP Development|http://www.sappress.com/product.cfm?account=&product=H1986] for the full story.
Greetings
Thomas -
Using SequenceFactory getNext in persistent object constructor
Hi,
Rightly or wrongly (maybe wrongly cos I am getting problems...)
In my persistent object constructors, I am initialising the objects id
field using the sequence factory getNext() method.
If I run the schematool on a blank DB with no tables then it works fine -
classes are enhanced, tables created.
But if I run it again on the same db, it fails on the first persistent
object, with this stack trace:
[java] java.lang.ExceptionInInitializerError:
javax.jdo.JDOFatalUserException: The system could not initialize; the
following registered persistent types are missing metadata or have not
been enhanced: [class com.rabobank.reef.tradeadapters.dto.ReefSystem].
[java] at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.loadPersistentTypes(JDBCPersistenceManagerFactory.java:293)
[java] at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.setup(JDBCPersistenceManagerFactory.java:256)
[java] at
com.solarmetric.kodo.runtime.PersistenceManagerFactoryImpl.privateSetup(PersistenceManagerFactoryImpl.java:872)
[java] at
com.solarmetric.kodo.runtime.PersistenceManagerFactoryImpl.getConnectionFactory(PersistenceManagerFactoryImpl.java:223)
[java] at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.setLogWriter(JDBCPersistenceManagerFactory.java:175)
[java] at com.rabobank.util.kodo.JDOFactory.<init>(Unknown Source)
[java] at com.rabobank.util.kodo.JDOFactory.getInstance(Unknown
Source)
[java] at
com.rabobank.util.kodo.JDOFactory.getNextPrimaryKey(Unknown Source)
[java] at
com.rabobank.reef.tradeadapters.dto.GenericObject.<init>(Unknown Source)
[java] at
com.rabobank.reef.tradeadapters.dto.ReefSystem.<init>(Unknown Source)
[java] at
com.rabobank.reef.tradeadapters.dto.ReefSystem.<clinit>(Unknown Source)
[java] at java.lang.Class.forName0(Native Method)
[java] at java.lang.Class.forName(Class.java:115)
[java] at
com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1115)
[java] Exception in thread "main"
Which looks like the sequence factory requires an initialised system to be
accessed, but it is trying to init the system when it is called?
But it works on a clean db...
I am just going about this the wrong way or is it a simple bug in my
procedure?
Thanks,
Chrisheres the exact error message im getting
Exception in thread "main" java.lang.NullPointerException
at instrument.<init>(instrument.java:15)
at iContainer.populate(iContainer.java:34)
at main.main(main.java:7)
the bolded line is the erroneous one
public instrument(int newID, String newType, String newRenters [], int newPrice, String newKey, boolean newNeedsRepairs)
super(newID);
type = newType;
for ( int x = 0; x < newRenters.length; x++)
*renters[x] = newRenters[x];*
price = newPrice;
key = newKey;
needsRepairs = newNeedsRepairs;
} -
Collection of non-persistent objects
Greetings
Is it possible to persist a Collection of non-persistent objects through the
kodo externalization feature? The non-persistent objects themselves are
externalizable, but I don't know how I would go about persisting a
Collection of them.
..droo.If you store them in some sort of externalized form in a single column it is
easy - just use externalization framework to ext and de-ext them to anf from
string. Couple of caveats you need to be aware of If your collection objects
are mutable:
1. You need to durty your collection field so it get prsisted on commit
2. on rollback Kodo will restore you collection content but not collection
member content. If they are mutable you will have to make their class
persistent with mapping "none" so they participate in transaction
"Drew Lethbridge" <[email protected]> wrote in message
news:BD0B44BF.544%[email protected]..
Greetings
Is it possible to persist a Collection of non-persistent objects throughthe
kodo externalization feature? The non-persistent objects themselves are
externalizable, but I don't know how I would go about persisting a
Collection of them.
.droo. -
Could not persist object with token:re00100000b7f6e12d419f(Error: INF)
Post Author: saravanan rangaraj
CA Forum: Migration to XI R2
Hi everybody,
I'm getting error, 'could not persist object with token:re00100000b7f6e12d419f(Error: INF)' while refreshing reports in infoview. If I logoff and logon it's working fine. The error repeats everytime after refreshing 3-5 reports.Can anybody say why it happens?Post Author: saravanan rangaraj
CA Forum: Migration to XI R2
Hi everybody,
I'm getting error, 'could not persist object with token:re00100000b7f6e12d419f(Error: INF)' while refreshing reports in infoview. If I logoff and logon it's working fine. The error repeats everytime after refreshing 3-5 reports.Can anybody say why it happens? -
Hi Gurus.,
I am little bit confused over Persistent Objects.. Y we need to use Persistent Objects.. Is it equal to Enquee/Dequee process of normal abap ..
Regards.,
S.SivakumarPersistent objects were introduced in ABAP OO in order to replace physical data manipulation via open SQL statements by more abstract OO-typical GET and SET methods for a persistent data object. Has nothing to do with Dequeue/Enqueue.
I recommend reading chapter 3 of [Next Generation ABAP Development|http://www.sappress.com/product.cfm?account=&product=H1986] for the full story.
Greetings
Thomas -
Hi Experts,
Does persistent object provide locking mechanism for updating data? If yes, How do I do it?
Thanks!Sure - it's called the Transaction Service. [ABAP - Object Services|http://help.sap.com/saphelp_nw70/helpdata/en/ab/9d0a3ad259cd58e10000000a11402f/frameset.htm]
Cheers
Graham Robbo -
PRO*C에서 OBJECT 예제 프로그램 (PERSISTENT OBJECT)
제품 : PRECOMPILERS
작성날짜 : 1998-11-25
PRO*C에서 object 예제 프로그램 (Persistent object)
==================================================
1. object type, object table를 생성하고, 데이타를 insert
drop table use_person
drop type person
create type person as object (
name varchar2(60),
address varchar2(200),
dob date,
age number(3,0)
create table use_person of person
insert into use_person values (
person('John Smith', '1 Somewhere', '10-jan-66', 32)
insert into use_person values (
person('Susan Jones', '2 Elsewhere', '16-may-72', 26)
2. OTT를 수행할 source를 생성한다.
(file명은 ojb_in.typ)
type person
3. OTT를 수행하여 person에 대응되는 c struct를 가지고 있는
obj.h를 생성한다.
ott intype=obj_in outtype=obj hfile=obj.h userid=scott/tiger
code=c
4. 예제 프로그램 <cache_obj.pc>
#include <stdio.h>
#include <string.h>
#include "obj.h"
/* VARCHAR 처리를 위한 macro. */
#define TERM(X) ( X.arr[X.len] = '\0' )
#define SLEN(X) ( X.len = strlen((char *)X.arr) )
EXEC SQL INCLUDE SQLCA;
EXEC SQL BEGIN DECLARE SECTION;
VARCHAR oracleid[20];
person person_ptr; / pointer로 선언됨에 주의*/
person_ind *person_ind_ptr;
person_ref *per_ref;
VARCHAR address[201];
VARCHAR birthday[21];
VARCHAR name[61];
int age;
EXEC SQL END DECLARE SECTION;
main()
char action_str[30];
EXEC SQL WHENEVER SQLERROR DO o_error(action_str);
/* Database에 connect */
strcpy( (char *)oracleid.arr, "scott/tiger" );
SLEN( oracleid );
strcpy( action_str, "connecting to d/b" );
EXEC SQL CONNECT :oracleid;
* client side object cache를 다루기 위해서는
* REF를 fetch 하여, 이를 이용하면 된다.
* REF를 할당하고, FETCH 하기
strcpy( action_str, "allocating ref");
EXEC SQL ALLOCATE :per_ref;
EXEC SQL DECLARE C1 CURSOR FOR
SELECT REF(p)
FROM USE_PERSON p
WHERE NAME = :name;
strcpy( (char *)name.arr, "John Smith" );
SLEN(name);
strcpy( action_str, "opening cursor" );
EXEC SQL OPEN C1;
strcpy( action_str, "fetching cursor" );
EXEC SQL FETCH C1 INTO :per_ref;
* cache에 있는 object에 대해 DEREF를 수행하고,
* FOR UPDATE문으로 해당 row에 대해 lock을 건다.
strcpy( action_str, "fetching object" );
EXEC SQL OBJECT DEREF :per_ref INTO :person_ptr:person_ind_ptr
FOR UPDATE;
/* address, dob 컬럼을 update하기. */
strcpy( action_str, "getting attributes" );
EXEC SQL OBJECT GET ADDRESS, DOB FROM :person_ptr:person_ind_ptr
INTO :address, :birthday;
TERM(address);
TERM(birthday);
printf("\nCurrent address is: %s", (char *)address.arr);
printf("\nCurrent birthday is: %s", (char *)birthday.arr);
strcat((char *)address.arr,", Nowhere Town");
SLEN(address);
strcpy((char *)birthday.arr,"12-jan-66");
SLEN(birthday);
strcpy( action_str, "setting attributes" );
EXEC SQL OBJECT SET ADDRESS, DOB OF :person_ptr:person_ind_ptr
TO :address, :birthday;
/* 변경 내용을 서버에 반영 */
strcpy( action_str, "marking object as updated" );
EXEC SQL OBJECT UPDATE :person_ptr;
strcpy( action_str, "writing update to database" );
EXEC SQL OBJECT FLUSH :person_ptr;
* object를 Release한다. 이때 unpin도 같이 수행된다.
* indicator인 경우에는 unpin 개념이 없다.
* object의 default DURATION은 transaction이기 때문에
* commit 이나 rollback을 수행하면 자동으로 unpin 된다.
* 만약 DURATION=SESSION으로 precompile을 했다면 오브젝트는
* 프로그램이 끝나거나, RELEASE문을 수행할때까지
* unpin되지 않는다.
strcpy( action_str, "unpinning object" );
EXEC SQL OBJECT RELEASE :person_ptr;
* Free the REF.
strcpy( action_str, "freeing ref" );
EXEC SQL OBJECT FREE :per_ref;
* commit하여 변경된 내용을 저장한다.
strcpy( action_str, "committing" );
EXEC SQL COMMIT;
* 다음은 object를 만들어 테이블에 insert 하는 방법이다.
* 즉, Cache에 object를 생성하여 이를 서버에 flush 시키는
* 방법이다. object를 ref로 선언하는 경우 그 object를
* return 하는데, persistent object로 선언하였기 때문에
* (즉, DB에 저장된object table) 이 REF는 DB 의 실제 row와
* 관련이 있다.
* REF 할당하기.
strcpy( action_str, "allocating ref");
EXEC SQL ALLOCATE :per_ref;
strcpy( action_str, "creating object" );
EXEC SQL OBJECT CREATE :person_ptr:person_ind_ptr
TABLE USE_PERSON
RETURNING REF INTO :per_ref;
* object indicator의 각 요소에 NOT NULL을 설정.
person_ind_ptr->atomic = OCIIND_NOTNULL;
* object와 indicator에 값을 설정하기
strcpy( (char *)name.arr, "Richard Mountjoy" );
SLEN(name);
strcpy( (char *)address.arr, "7 The Butts, Silchester" );
SLEN(address);
strcpy( (char *)birthday.arr, "16-nov-73" );
SLEN(birthday);
age = 24;
strcpy( action_str, "setting attributes" );
EXEC SQL OBJECT SET NAME, ADDRESS, DOB, AGE
OF :person_ptr:person_ind_ptr
TO :name, :address, :birthday, :age;
person_ind_ptr->NAME = OCI_IND_NOTNULL;
person_ind_ptr->ADDRESS = OCI_IND_NOTNULL;
person_ind_ptr->DOB = OCI_IND_NOTNULL;
person_ind_ptr->AGE = OCI_IND_NOTNULL;
* insert하기 위해 db에 object를 Flush하기
strcpy( action_str, "writing object to database" );
EXEC SQL OBJECT FLUSH :person_ptr;
strcpy( action_str, "unpinning object" );
EXEC SQL OBJECT RELEASE :person_ptr;
strcpy( action_str, "commiting" );
EXEC SQL COMMIT;
* REF는 실제 메모리가 할당되는 것이기 때문에, commit
* 된다 하더라도 메모리가 free되지 않는다. (DURATION이
* transacetion이라고 하더라도)
* object를 return한 REF는 DB에 저장되어 있는 object가
* 유용한지를 보여주는 용도로 사용할 수 있다.
* 어떤 값이 object에 copy되어 return되는 지는 version
* precompile option에 의해 결정된다.
* RECENT (default) : 현재 transaction에서 fetch했다면
* cache로부터 object를 return 하고,
* 아닌 경우는 db로 부터fetch를 하게
* 된다.
* ANY : 원래 어떤 값을 fetch했는 지에 관계없이 cache에
* 있는 값을 return 의미
* LATEST : DB로 부터 refetch
* 이 sample에서는 object를 release한 상황에서, db로 부터
* fetch했음을 보이기 위해 VERSION을 LATEST로 설정했다.
EXEC ORACLE OPTION (VERSION=LATEST);
strcpy( action_str, "fetching object" );
EXEC SQL OBJECT DEREF :per_ref INTO :person_ptr:person_ind_ptr;
* 초기화를 하면 indicator를 check할 필요가 없다.
name.len = 0;
address.len = 0;
birthday.len = 0;
age = -1;
strcpy( action_str, "getting attributes" );
EXEC SQL OBJECT GET NAME, ADDRESS, DOB, AGE
FROM :person_ptr:person_ind_ptr
INTO :name, :address, :birthday, :age;
printf("\n\nAttributes of newly created object are:");
TERM(name);
TERM(address);
TERM(birthday);
printf("\nName: %s", name.arr);
printf("\nAddress: %s", address.arr);
printf("\nBirthday: %s", birthday.arr);
printf("\nAge: %d", age);
* Clear up.
strcpy( action_str, "unpinning object" );
EXEC SQL OBJECT RELEASE :person_ptr;
strcpy( action_str, "freeing ref" );
EXEC SQL OBJECT FREE :per_ref;
EXEC SQL WHENEVER SQLERROR CONTINUE;
EXEC SQL ROLLBACK WORK RELEASE;
printf("\n");
int o_error( action_str )
char *action_str;
int i;
char error_str[150];
EXEC SQL WHENEVER SQLERROR CONTINUE;
for ( i = 0; i < sqlca.sqlerrm.sqlerrml; i++ )
error_str[i] = sqlca.sqlerrm.sqlerrmc;
error_str[i] = '\0';
printf( "\nFailed with following Oracle error while %s:\n\n%s",
action_str, error_str );
EXEC SQL ROLLBACK WORK RELEASE;
exit(1);
5. 프로그램 수행 결과
Current address is: 1 Somewhere
Current birthday is: 10-JAN-66
Attributes of newly created object are:
Name: Richard Mountjoy
Address: 7 The Butts, Silchester
Birthday: 16-NOV-73
Age: 24Thanks so much, Bob.
My printer requires that I use the PDF/X-1a:2001 standard for PDF export, which means that it must be Acrobat 4 or later compatibility.
Also: I don't see how to NOT flatten, when exporting PDF for print; the options for flattening are "low resolution," "medium resolution," or "high resolution"—but there is not an option to NOT flatten. Do you know a work-around for this?
Maybe you are looking for
-
Safari is slow to open and close. It also slows down other apps while it is running. How can I resolve this issue?
-
Downgraded to itunes 6.0.5 and still having problems. HELP
I just downgraded from 7 to 6.0.5 and for whatever reason itunes still slows down the whole works when ripping, rips at really slow (3-4x) speeds, and plays all garbled when trying to do more than one thing at a time (i.e. use any other program in co
-
i have a 3d demo reel i wanna show to potential employers 640 by 480 DV .....3.5 mins....quicktime h.264....29.97...size 550 mb problem 1: I thought about simply adding the video file itself to a DVD but when on other computers ( two differint laptop
-
International Buyers trying to pay with PayPal
I've had a number of customers contact me that they are having problems purchasing. The common factors seem to be that they are International and trying to use PayPal to pay. One person I was able to get working by having her sign in to Adobe using t
-
Am I missing something regarding database queries from BPEL?
Hi, I'm trying to execute what I would think is a simple query from within a BPEL process against an Oracle 10g database. I have a root table, meter_reading that has an id, a time, a value, and a foreign key to a meter_reading_type table with a simpl