Version control in labview ?

How to change from latest version to previous version
For example
I created a project by naming it as version 1.
Later my colleague edited the same project and named it as version 2.
Now with help of labview can i extract the files of version 1 ? And compare the difference between Version 1 and version 2 .

Hello Dennis_Knutson & P Anand Thanks for you reply
I dont have any version control system . can i have the link for pro pro version please   @  Dennis_Knutson

Similar Messages

  • LabVIEW with version control

    Hi,
          I am using LabVIEW with version control and only want to check out the VI which I need to modify. If I changed a subVI all the VIs directly or indrectly called this VI got recompiled and in order to save them I need to check out all the VIs are affected. If I only check out the file I need to modify and ignore other recompiled VIs the problem is if I use typedef ENUM and I still want the automatically updated VI got saved. Does anybody run into this problem?
        Thanks for help!
        Regards,
        Tom
    Solved!
    Go to Solution.

    Yes, it can be a problem since LabVIEW stores the source and compiled code in the same file. There is an option to separate source from compiled code that addresses this problem. I have never used it and don't know if it causes any other problems.
    =====================
    LabVIEW 2012

  • PVCS version control integration in LabVIEW?

    I am currently using the free 2 client Perforce software with LabVIEW.  It works well for my needs, as we have only 2 developers working on this project.  However, we were just got bought out by a larger company that uses Serena PVCS for their version control.  We are transitioning to their IT system and I need to transfer everything to a new server anyway, so was considering trying PVCS instead. 
    I would love to hear about anyones experience with PVCS integrated with LabVIEW?  Or even better, if anyone has the experience to compare PVCS with Perforce in terms of LabVIEW integration?  I need to weigh the two options. 
    Thanks for your help!
    Rebecca 
    Rebecca Abbott
    Serica Technologies, Inc.

    Nothing much yet, but I found a website that has the batch file for integration with SVN.
    Guess I have to contact the author to get more details:
    http://arwaheem.wordpress.com/2008/04/30/siebel-version-control-source-code-integration-using-sub-version/

  • Poll - Which Version Control Software Do You Use With LabVIEW?

    I wish the forums had a poll feature. I created a poll in the developer community - Which Version Control Software Do You Use With LabVIEW?
    http://decibel.ni.com/content/polls/1818
    Edit: I just saw that there already is a poll for that
    http://decibel.ni.com/content/polls/1050
    =====================
    LabVIEW 2012

    julieann wrote:
    You can use a source control provider to share files among multiple users, improve security and quality, and track changes to shared projects. Use LabVIEW with third-party source control providers so you can check out files and track changes from within LabVIEW. See info. here.
    Looks suspiciously like someone trying to increase hits on their blog. A coincidence that it was posted the same day as the blog post?
    Message has been reported to the moderator. Laura can decide whether or not it's appropriate.

  • Version control tool for Mac OS X?

    Hi all
    If using labview on Mac OS X, 
    do you have some version control tools to recommend?
    Thanks  a lot

    As far as i know, LV for Mac does not integrate with source code control provider. LV for Windows has two requirements for this:
    a) Professional Development Environment
    b) A source code control provider compatible to the Microsoft Source Interface
    There is still always (Mac, Linux and Windows alike) the possibility to control source files using the SCC providers client software.
    Many open source project SCCs like CVS or Git integrate, at least in Windows, in the File Explorer.
    I recommend you to research possible solutions like this for Mac.
    The next question is if you want to use a distributed SCC or a local one. Depending on this, you will have to setup a network server with compatible provider (e.g. RhodeCode).
    LV provides both a Diff and Merge tool as EXE (Professional). I am not sure if this is also true for the Mac version, so look for "LVCompare" and "LVMerge".
    hope this helps,
    Norbert
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Version control (lvcompare and lvmerge) for projects, classes and libs?

    Hi everyone
    Version control for classes, projects and libs (not just a plain .vi) - can it be done with lvcompare and lvmerge?
    I've tried a simple "LVCompare.exe project1.lvproj project2.lvproj" and it only returns an error (lvcompare.exe vi1.vi vi2.vi works). So this is maybe a dead end.
    How do you guys version control more complex projects? E.g. projects which use classes, libs, labview projects (.lvproj)?
    Best regards
    Jonascj

    Thank you for your reply. You are right, .lvclass, .lvproj and .lvlib are all just xml files - I've just figured that out my self when I accidentally called GIT's default diff on a lvclass
    I've also just spoken to National Instruments. The person I spoke to (from the one of the danish offices) told me that no tools exist at this time (2013-04-08) which will compare those LabView file types, but that there was an internal (National Instruments themselves)  feature request for such tools.
    He also told me another interesting thing which I did not know. The lvcompare.exe (located in National Instruments/Shared/LabVIEW Compare/ on Windows) is actually the not developed by National Instruments, but is either a "fork" of LVDiff (http://meta-diff.sourceforge.net/) or LVDiff renamed. So one could simply obtain the source code from http://meta-diff.sourceforge.net/ (at the bottom of the page "Win32 binary w/source") and add a few property nodes to do comparision of lvclass attributes etc.

  • Version control and multiuser access on one project

    Hello,
    I have a question is there a tool from National Instruments or a third party supplier, with which I can controll the programmed versions of the LabVIEW Code and makes it possible that more than one person works at one time at a project.
    Best regards
    TED

    Ted,
    Please refer to the discussion topic (...LabVIEW>LabVIEW General>Topics...) regarding Programming guidelines. There is a bit of discussion in that thread about source code control and project management.
    This is a very difficult subject to learn, especially when applied to LabVIEW coding, as all the information out there is strictly limited to text based programming.
    I suspect (I know for a fact...) that there are materials in the works that would pertain to this exact subject. Keep your eyes on the NI website under reference materials that may speak of such subjects.
    Good luck

  • Simple motor control with Labview

    Can anyone suggest a simple motor to be controlled by labview. I am interested in making a small scale elevator that is controlled with a labview interface. If anyone could point me in the right direction it would be greatly appreciated. - Bryan

    Attached is the vi for the program.  I will also try and attach the C code for the project.  It took a lot of failed attempts to get it working so I hope this works for you.  I don't have a schematic for you, but if you look over the C code it should let you know.  Also I used the CCS development kit 16F877A.  I'm not great at programming in C so there is a good chance you can clean it up a bit.
    I'll keep an eye on this post if you have any questions, when winter comes I'll probably work on this some more.
    Message Edited by nutmegzzzz on 09-19-2005 01:56 PM
    Attachments:
    Serial Read with Timeout version 1b.vi ‏169 KB
    LED and Motor Control from LabView - Complete.c ‏3 KB

  • How do I fix project after "Remove From Version Control" corrupted it?

    I am using RoboHelp 9.0.1 and installed both Tortoise SVN 1.6.9 and latest PushOK SVNSCC then added my large RoboHelp project to SVN. I was able to check in and out files from SVN but had several issues with it:
    1) Super super slow. Working with folders or any renames would take 10 seconds per file and up to 1 hour if needed to refresh the root folder.
    2) I could not perform some actions at all, such as delete, rename, or move folders. I kept getting COM errors.
    I therefore decided that working with SVN and RoboHelp is not practical, at least not on my VPN so I decided to disconnect the project from source control and just work locally. The only option that I saw that sounded like it would do that was the "Remove from Version Control". This started a process that lasted for several hours. At the end of it, I now have several significant issues:
    1) The order of the files and folders in my Project Manager is completely wrong now. I have almost 1000 topics and reordering all of them is not possible.
    2) The Table of Contents, Glossary, and Index files appear empty. They had content before.
    2) A couple of the Single Source Layouts I had created are completely missing.
    3) Many, but not all, of the folders have tons of files with the extension ending in "_temp_removed_by_svn"
    4) Many, but not all, of the files are actually gone from SVN so I can't recover a clean image. There was no warning that this command would actually delete the files from SVN (I thought it would just remove the version control connection).
    5) Who know what other issue exist that I haven't seen.
    Any idea how I can fix this?
    Thanks in advance,
    Dan

    Are the "_temp_removed_by_svn" files in your local folder or SVN? Let us know how you get on with the new project. It sounds like something is wrong with SVN. Can you use the SVN Log command to see whether there is a different version you can restore. This might also give you an indication of what might have caused the problem. You could try deleting your CPD file. It gets rebuilt it is isn't there anyway. This file can become bloated and it is good practice to delete it when it gets close to 2mb in size. Your project is fairly large and has a lot of folders and may affect performance. Have you considered splitting them and merging the output? I know you probably don't want to consider this right now, but I think it may be a better long term solution.
      The RoboColum(n)
      @robocolumn
      Colum McAndrew

  • Can I have a library of PDF docs with version control? Can it cope with version nos. embedded in the file name?

    I manage a set of documents which are edited in Word but "published" as PDFs (using Word 2010's save to PDF capability).
    I want to create a library for them on SharePoint (my company has SharePoint Online via its Office 365 subscription).
    I'm pretty much a SharePoint novice but even I can see it's easy to upload the documents to a simple library. The things that are giving me a headache are:
    Can I tell SharePoint what the version number of the uploaded PDF document is? The version number as understood by the library needs to match the version number written into the document (where it is called a revision number and increments in whole numbers
    starting from zero).
    How do I handle replacing the uploaded PDF documents with new versions? If they were Word documents I could edit them by opening them from the SharePoint library, checking them out if necessary, and SharePoint would handle version control.
    But since the PDFs are generated from editable masters (Word documents) which are NOT on SharePoint I would need to edit the local Word document on my PC then generate a PDF version then upload it to replace the existing PDF document in the
    library. Is it easy to upload a new document over the top of an old in a SharePoint library?
    Hoping someone can give me some answers.
    Regards,
    Bruce Officer

    hi Bruce,
    1. It sounds like what you need is to set the starting version number since your revision number increments in whole numbers, it would match up to SharePoint once the starting version number is set. You can potentially create a new custom field in the
    library to manually track the version of the uploaded PDF document, but this might not match up with SharePoint's own version number and could get confusing. Another possibility is to upload dummy versions of the PDF document until the SP version
    matches with the revision version and then delete these dummy versions.
    2. When you upload the PDF document again into the library, it should prompt you to see if you want to replace the existing. If you proceed with the upload, it should replace and increment the SharePoint version number.
    Please Mark Answered if my reply solves your problem. Thanks!
    Jeff Thai
    Technical Solutions Architect, AvePoint
    http://www.AvePoint.com

  • Can I run two separate versions of the LabVIEW Run-Time Engine on one PC?

    Hello, I am curious if anyone knew if it is possibly to install and use two separate versions of the LabVIEW Run-Time Engine on one PC?  I currently have the 2009 Run-Time Engine installed on one machine and wanted to install the 2011 Run-Time Engine as well. I know that you can run two separate versions of the LabVIEW program on one machine, but what about the Run-Time Engine?
    Thanks!
    Solved!
    Go to Solution.

    I'm guessing this is a bug that NI needs to fix.  I see no reason you shouldn't be able to install the run-time engine of an older version.  I'd be interesed in if it allows you to install the older development environment, which also includes the older run-time engine.  There are some command line switches for NI installers as mentioned here:
    http://digital.ni.com/public.nsf/allkb/C361087EE9F20810862577850073128E
    I wonder if there is a force install option.
    Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
    If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

  • Regarding version control

    Hi,
    Could u please help me out in giving some ideas of version control in sap?
    First let me give some example as follows:
    First if i develop something in the developement server then later when i transfer to the QA server and later to production server then is there any change in version.
    Please give me a details of this issue????
    Thanks,
    Batista....

    hi priya,
    Version Control
    Version control is a mechanism that helps maintaining the revision history of a development resource and tracking the changes done to it. It defines a set of constraints on how a development resource can be changed. A development resource that complies with the constraints defined by the version control is called a versioned resource. When a versioned resource is modified or deleted, a new version is created for the resource. A unique sequence number is associated with each version of the resource created in a particular workspace. This sequence number identifies the order in which the versions were created in that workspace. The DTR graphically represents the relationship between the different versions of a versioned resource in the form of a version graph.
    For the representation of version graphs, this document follows the conventions shown in this figure.
    The figure shows the meaning of the symbols in the version graph.
    The following changes are tracked by the version control mechanism of the DTR:
    ·        Addition of the resource to the repository
    ·        Modification of the resource in the repository
    ·        Deletion of the resource from the repository
    In all the above cases, a new version of the resource is created.
    Production Delivery
    Packaging
    To deliver your product, you have first to package it. There are different packages you can use for shipping your product to your customers:
    ●      Software Component Archives (SCAs) – this is the standard way to deliver software for the SAP NetWeaver platform.
    ●      Software Deployment Archives (SDAs) – for top-level applications you can deliver only the executable part of the software. You can directly deploy the SDA file.
    ●      Public Part Archives (PPAs) in Development Component Interface Archives (DCIAs) – for reusable components (Java EE server libraries, Web Dynpro components, Visual Composer components and so on). You can deliver only the metadata of the components. DCIA can be included in SCA file too.
    How to do that?
    Using the command line tool provided with the SAP NetWeaver Composition Environment you can:
    ●      package a collection of components into an SCA including only the deployable archives. This is required if you do not want others to reuse the delivered components.
    ●      package a collection of components into an SCA including the deployable archives and the corresponding interface archives. This allows customers to develop against these components. Those customers can directly import the SCA into their own SAP NetWeaver Development Infrastructure (NWDI) or into an SAP NetWeaver Developer Studio local installation.
    ●      package the public parts of a component together with the required metadata into a DCIA (and further into an SCA).
    ●      include source code into an SCA.
    ●      unpack a deliverable archive and drop the result into an existing version control system for example, or directly import them into an existing Design Time Repository (DTR).
    Delivery of Source Code for Further Customization
    In addition, you can deliver source code to your customers to allow further customizing or add-on development. The deliverable archive may contain sources for:
    ●      individual development components (DCs).
    ●      a collection of development components, for example a whole software component (SC).
    Example
    A customer can add a new source compartment to an existing configuration, and then locate that compartment in the file system where it is accessible by the version control system in charge. Then he or she extracts the sources with the command line tool to the compartments root directory and refreshes the configuration in the SAP NetWeaver Developer Studio. The compartment tree is populated with components from the archive. Afterwards, the customer may put those components under version control. Deliverables that contain only individual components may be treated accordingly.
    This mechanism may also be used for other purposes, for example for setting up a simple backup and restore mechanism for components in Developer Studio, or sharing DC sources without having a central version control system: a developer may pack a compartment and store the resulting SCA on a central share or backup system. Another developer may take that SCA and import it.
    Limitations
    Note the following limitations connected with this kind of source code delivery:
    ●      There is no support for handling conflicts when different actors in a delivery chain develop independently in the same source code. You cannot prevent the customer from modifying delivered sources. When you ship a new version of the sources, there is no special support for updating and no support for merging the update with modifications done by the customer. You and the customer have to agree on a process how those conflicts are handled. For example, the customer can decide not to import the update you deliver directly into the active development line, but to unpack the delivered sources to some unconnected sandbox system and perform the required merges manually.
    ●      When you deliver source code to customers, it is important that you also deliver the required libraries and generators that are needed to build these sources. For example, it may be necessary to ship some archive compartments that contain used components.
    ●      There is no support for delivering deletions in a new version. If a source file was deleted, the customer has to manually ensure that the file is also deleted in the Developer Studio or source code management system.
    ●      If a customer prefers to work with the SAP NetWeaver Development Infrastructure (NWDI), this customer cannot directly import the source delivery package into the NWDI landscape. Between NWDI landscapes at different places, sources usually are exchanged through a more sophisticated export format that contains not only the pure source code, but also the versioning meta information of the exporting DTRs. This ensures that the importing repository can detect conflicts that arise due to modifications. If this versioning information is not available, the only way to import source deliveries is to unpack them to a file system and manually put them under version control with the Design Time Repository perspective of the Developer Studio. In case of an update, the customer would have to check out all affected files, merge them with the new versions from the source delivery, and finally check them in as a new version.
    More information: Composition Environment Command Line Tool
    see this url
    http://www8.sap.com/businessmaps/0134713B1D6046C59DE21DD54E908318.htm
    thanks
    karthik
    reward me if usefull

  • Oracle Service Bus Configurations version control and deployment automation

    Hi,
    Currently we have OSB10gR3 installed and we use the web based sbconsole to create projects and proxy services. It's all working well and good!!
    We are at the state where we need to think about source control, migration of artifacts from dev to test and to prod.
    I'm looking for pointers to version control the artifacts of OSB projects, what could be version controlled (no binaries) and how do we extract those artifacts?
    How do we customize those artifacts while migrating to different environments in an automated fashion?
    Please point me to best practices and gotchas that we should be aware of while dealing with deploying OSB proejcts from test to Prod.
    Thanks in Advance!!

    After reading the threads mentioned by Deba, I'm able to get this all worked out with SBConsole itself. Experts, please review my approach below and let me know if I have overlooked anything.
    Simple advantage I see in using sbconsole is that it requires less maintenance, i.e. avoids rolling out another IDE (Eclipse -Workshop plug-in) to IT developers and at the same time provides the functionality that we are looking for. Currently, JDeveloper is our primary IDE, so we thought it's best to wait till OSB development gets integrated into JDev.
    This is the deployment workflow which worked for us,
    Developer:
    1)Develops Proxy services using SBconsole in Dev environment.
    2)Creates sbconfig.jar by using the export functionality available in System Administration link in sbconsole
    3)Checks-in ALL the files present in the above jar into version control under the proxy service project name
    4) Creates customization file using the customization file link in System Administration and modifies the value for each environment i.e. creates two files test_customfille, prod_customfile
    5)Checks-in the customization files into version control under the same proxy service project
    Promotion to Test and Prod
    1) From the source control, service proxy is built (actually the jar file of all files including the custom file is created)
    2) SCP proxy_sbconfig.jar file to Test or Prod box
    3) Follow the steps mentioned in Auto deploy of ALSB/OSB artifacts - Proxy, WSDL and webservices...
    4) Depending on the server, test or prod, pick the right customization file and deploy using ANT.
    Thanks!!

  • Oracle 10g R2 - Metadata Issue With Version Controlled Resources

    We are trying to utilize the Oracle 10g R2 feature that allows user-defined metadata to be attached to XML DB resources. However, we are encountering errors when we try to append/attach metadata to a version-controlled resource (VCR). The following steps were followed:
    1. Register a new schema to be used for metadata (XMLSCHEMA.registerSchema).
    2. Add a new resource to to the XML DB and make it version controlled (DBMS_XDB.createResource and DBMS_XDB_VERSION.makeVersioned).
    3. Checkout the newly created version-controlled resource (DBMS_XDB_VERSION.checkout)
    4. Add metadata to the version-controlled resource (DBMS_XDB.appendResourceMetadata)
    However, after step 4, the errors shown below are encountered:
    ========================================================
    begin
    ERROR at line 1:
    ORA-00600: internal error code, arguments: [qmxStrCopy: INLOB 2], [], [], [],
    ORA-06512: at "XDB.DBMS_XDB", line 890
    ORA-06512: at line 2
    ========================================================
    The steps followed for adding metadata to a resource were taken from Chapter 26 of the "Oracle XML DB Developer's Guide 10G Release 2" (http://download-east.oracle.com/docs/cd/B19306_01/appdev.102/b14259/xdb_repos_meta.htm#sthref2302).
    Is is possible to append and maintain metadata to an XML DB version controlled resource (VCR)? If so, what are the correct steps to do this? Note that if this is tried with a resource that is not version controlled, then no errors are encountered.
    Thanks,
    Steve

    It appears that this issue has been solved in the next release of the database
    QL> spool testcase.log
    SQL> --
    SQL> connect &1/&2
    Connected.
    SQL> --
    SQL> var schemaURL varchar2(256)
    SQL> var schemaPath varchar2(256)
    SQL> var resourcePath varchar2(256)
    SQL> --
    SQL> begin
      2    :schemaURL := 'metadata.xsd';
      3    :schemaPath := '/public/metadata.xsd';
      4    :resourcePath := '/public/metadataTest.txt';
      5  end;
      6  /
    PL/SQL procedure successfully completed.
    SQL> call dbms_xmlSchema.deleteSchema(:schemaURL,4)
      2  /
    Call completed.
    SQL> declare
      2    res boolean;
      3    xmlSchema xmlType := xmlType(
      4  '<?xml version="1.0" encoding="UTF-8"?>
      5  <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" elementFormDefault="qualified" attributeFormDefault="unqualified" xdb:storeVarrayAsTable="true">
      6          <xs:element name="root" type="rootType" xdb:defaultTable="METADATA_TABLE"/>
      7          <xs:complexType name="rootType" xdb:SQLType="METADATA_ROOT_T">
      8                  <xs:sequence>
      9                          <xs:element name="child" type="childType"/>
    10                  </xs:sequence>
    11          </xs:complexType>
    12          <xs:complexType name="childType" xdb:SQLType="METADATA_CHILD_T">
    13                                  <xs:sequence>
    14                                          <xs:element name="Child1" type="xs:string"/>
    15                                          <xs:element name="Child2" type="xs:string"/>
    16                                  </xs:sequence>
    17          </xs:complexType>
    18  </xs:schema>
    19  ');
    20  begin
    21    if (dbms_xdb.existsResource(:schemaPath)) then
    22      dbms_xdb.deleteResource(:schemaPath);
    23    end if;
    24    res := dbms_xdb.createResource(:schemaPath,xmlSchema);
    25  end;
    26  /
    PL/SQL procedure successfully completed.
    SQL> begin
      2    dbms_xmlschema.registerSchema
      3    (
      4      :schemaURL,
      5      xdbURIType(:schemaPath).getClob(),
      6      TRUE,TRUE,FALSE,TRUE,
      7      enableHierarchy=>DBMS_XMLSCHEMA.ENABLE_HIERARCHY_RESMETADATA
      8    );
      9  end;
    10  /
    PL/SQL procedure successfully completed.
    SQL> declare
      2    res boolean;
      3  begin
      4    if dbms_xdb.existsResource(:resourcePath) then
      5      dbms_xdb.deleteResource(:resourcePath,4);
      6    end if;
      7    res := dbms_xdb.createResource(:resourcePath,'Mary Had a Little Lamb');
      8  end;
      9  /
    PL/SQL procedure successfully completed.
    SQL> commit
      2  /
    Commit complete.
    SQL> select xdbUriType(:resourcePath).getClob()
      2  from dual
      3  /
    XDBURITYPE(:RESOURCEPATH).GETCLOB()
    Mary Had a Little Lamb
    SQL> declare
      2    resid raw(16);
      3  begin
      4    resid := dbms_xdb_version.makeVersioned(:resourcePath);
      5  end;
      6  /
    PL/SQL procedure successfully completed.
    SQL> commit
      2  /
    Commit complete.
    SQL> begin
      2    dbms_xdb_version.checkout(:resourcePath);
      3  end;
      4  /
    PL/SQL procedure successfully completed.
    SQL> commit
      2  /
    Commit complete.
    SQL> set long 10000 pages 0 lines 150
    SQL> --
    SQL> select r.res.getClobVal()
      2    from resource_view r
      3   where equals_path(res,:resourcePath) = 1
      4  /
    <Resource xmlns="http://xmlns.oracle.com/xdb/XDBResource.xsd" Hidden="false" Inv
    alid="false" VersionID="1" ActivityID="0" Container="false" CustomRslv="false" V
    ersionHistory="false" StickyRef="true">
      <CreationDate>2006-06-10T05:01:25.355009</CreationDate>
      <ModificationDate>2006-06-10T05:01:25.355009</ModificationDate>
      <DisplayName>metadataTest.txt</DisplayName>
      <Language>en-US</Language>
      <CharacterSet>UTF-8</CharacterSet>
      <ContentType>text/plain</ContentType>
      <RefCount>1</RefCount>
      <ACL>
        <acl description="Public:All privileges to PUBLIC" xmlns="http://xmlns.oracl
    e.com/xdb/acl.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:sch
    emaLocation="http://xmlns.oracle.com/xdb/acl.xsd                           http:
    //xmlns.oracle.com/xdb/acl.xsd">
          <ace>
            <grant>true</grant>
            <principal>PUBLIC</principal>
            <privilege>
              <all/>
            </privilege>
          </ace>
        </acl>
      </ACL>
      <Owner>SCOTT</Owner>
      <Creator>SCOTT</Creator>
      <LastModifier>SCOTT</LastModifier>
      <SchemaElement>http://xmlns.oracle.com/xdb/XDBSchema.xsd#binary</SchemaElement
    >
      <Contents>
        <text>Mary Had a Little Lamb</text>
      </Contents>
      <VCRUID>15DE79F263F7CC00E040578C2A0656F8</VCRUID>
    </Resource>
    SQL> begin
      2    dbms_xdb.appendResourceMetadata(:resourcePath,xmltype(
      3  '<root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      4         xsi:noNamespaceSchemaLocation="metadata.xsd">
      5      <child>
      6        <Child1>AAA</Child1>
      7        <Child2>BBB</Child2>
      8      </child>
      9  </root>'));
    10  end;
    11  /
    PL/SQL procedure successfully completed.
    SQL> commit
      2  /
    Commit complete.
    SQL> select r.res.getClobVal()
      2    from resource_view r
      3   where equals_path(res,:resourcePath) = 1
      4  /
    <Resource xmlns="http://xmlns.oracle.com/xdb/XDBResource.xsd" Hidden="false" Inv
    alid="false" VersionID="0" ActivityID="0" Container="false" CustomRslv="false" V
    ersionHistory="false" StickyRef="true">
      <CreationDate>2006-06-10T05:01:25.355009</CreationDate>
      <ModificationDate>2006-06-10T05:01:25.558913</ModificationDate>
      <DisplayName>metadataTest.txt</DisplayName>
      <Language>en-US</Language>
      <CharacterSet>UTF-8</CharacterSet>
      <ContentType>text/plain</ContentType>
      <RefCount>1</RefCount>
      <ACL>
        <acl description="Public:All privileges to PUBLIC" xmlns="http://xmlns.oracl
    e.com/xdb/acl.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:sch
    emaLocation="http://xmlns.oracle.com/xdb/acl.xsd                           http:
    //xmlns.oracle.com/xdb/acl.xsd">
          <ace>
            <grant>true</grant>
            <principal>PUBLIC</principal>
            <privilege>
              <all/>
            </privilege>
          </ace>
        </acl>
      </ACL>
      <Owner>SCOTT</Owner>
      <Creator>SCOTT</Creator>
      <LastModifier>SCOTT</LastModifier>
      <SchemaElement>http://xmlns.oracle.com/xdb/XDBSchema.xsd#text</SchemaElement>
      <Contents>
        <text>Mary Had a Little Lamb</text>
      </Contents>
      <VCRUID>15DE79F263F7CC00E040578C2A0656F8</VCRUID>
      <Parents>15DE79F263F8CC00E040578C2A0656F8</Parents>
      <root xmlns="" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNam
    espaceSchemaLocation="metadata.xsd">
        <child>
          <Child1>AAA</Child1>
          <Child2>BBB</Child2>
        </child>
      </root>
    </Resource>
    SQL> quit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.0.0 - Alpha
    With the Partitioning and Data Mining options
    I've filed bug 5313655 for the 10.2.x behavoir. If this is important to you you might want to consider signing up for the forthcoming beta program for the next release of the database

  • Application size in terms of pages and performance and Version Control

    Currently I'm looking into the best way to version control our APEX applications. From other threads, it seems it's an area that leaves much to be desired. We are on the verge distributing a large APEX project commercially but I cannot find a suitable versioning method to support bug fixes and new development happening at the same time to the same set of applications. I just hope everyone out there realises versioning is a vital area of the development process and VOTES for it in the V3 poll.
    Anyway, enough of the my whinging. I did have a brain wave (quite rare !). What would the drawback be to have only 1 or 2 pages per application. This would allow a developer to always import the application at the start of work (ie from versioning software such as VSS or PVCS) and then export it at the end back into say PVCS. The application has everything self contained and correct versions etc.
    This would allow more developers to work on different areas at the same time as opposed to having many pages in the one application where developers could step on each others toes etc. I've considered importing/exporting pages but the fact you cannot lock shared objects means there is a possibility that if many developers are working on the same application someone will change something that affects pages other than their own. It would also be a nightmare to tie up different versions of of pages, shared objects, applications etc. Would there a performance problem with this method ? Incidentally, why can't TABS be shared/subscribed across applications. It means they have to be created separately in each application whereas things like Nav Bars and Templates can be shared across applications.
    Currently, my thoughts are that: bug fixing for a production release has to be in a separate stream (apex installation) from say new development work for the same set of applications BUT what this means is that the bug fixes have also to be manually applied in the new development stream - which is a considerable overhead (ie twice the work).
    Thanks for hearing me out - assuming you survived to the end !
    Any encouraging comments would be appreciated !

    Wim,
    I don't entirely understand the behavior. There should be little/no difference between the two cases. I'm assuming you have no indexes, which isn't recommended for such large containers anyway. Can you make your document set available to me so I can see if I can reproduce the behavior and look at it more closely? A single container, or dbxml_dump of a container is sufficient (both compress well).
    Contact me directly at george dot feinberg at you know where.
    George

Maybe you are looking for