Generation of DDL dimension

When generating the DDL for a dimension of attribute Clauses are repeated. For example:

ATTRIBUTE city LEVEL city DETERMINES
CITY_NAME_STR
State LEVEL ATTRIBUTE DETERMINES the State
STATE_NAME_STR
Country LEVEL DETERMINED ATTRIBUTE
COUNTRY_NAME_STR
ATTRIBUTE LEVEL County DETERMINES
COUNTY_NAME_STR
State LEVEL ATTRIBUTE DETERMINES the State
STATE_NAME_STR

Hi DW,.

Thanks for your comments. I was able to reproduce after dimensional model to model physical Oracle engineering. Problem appears where there is more then a dimension set hierarchy.
I logged a bug for this.

Philippe

Tags: Database

Similar Questions

  • How to specify a script of overall pre for all generations of ddl

    Hello world

    I use SQL Developer Modeler data to generate both create and modify ddl scripts.

    These scripts can be quite long, if several objects are affected.

    When I run these scripts, because they are generated, I might lack of errors produced, as the

    These scripts execution simply continues to the next step.

    So what I do, is add "when sqlerror exit rollback" manually at the beginning of the script.

    I know, it is possible to specify a script for an object (e.g. table) before.

    What will answer me, because is an option to specify such a 'global' Pre script, which is automatically added to the

    the start of any product create or modify the script.

    Is there a way to do this?

    Kind regards

    J.P..

    Hi JP,

    There is no support for global Pre script.

    end your problem - you can define that behavior in your execution environment depending on how you run generated DDL, or you can try the generation 'Advanced DDL' option - it you can also set errors to be ignored and more options for unloading data to the filesystem if the table is re-created.

    Philippe

  • Bad generation of DDL for indexes primary key partitioned - lost partitions

    Hello

    In our design of the database, we want to divide some tables and their indexes. The partition type is hash indexes must be local, also divided No problem affecting storage of the table partitions. Also no aucun probleme problem with the index partitions, not included the primary key.

    Our problem appears in the generation of DDL: partitions of tables and indexes are generated fine except the primary partitions it shows key - phrase-'alter table' primary key as if it was not partitioned.

    Apparently indexes primary keys must be generated as the other indices, is it not?

    Thanks in advance,

    Bernat Fabregat

    Published by: Berni 11/29/2010 12:37

    Hello Bernat,

    for local partitioning, you need to create indexes separated on column PK (if you do not already). Set partitioning for this index, and then in the dialog box for the primary key in the physical model:
    (1) in the 'Général' tab, clause "with the help of the index' - select 'by the name of the index.
    (2) in tab 'using Index' - 'Existing Index' drop-down list box - select defined index.

    Global partitioning can be created directly on the primary key in the physical model.

    Philippe

  • Generation of DDL works do not, after restart Open-Petite not found

    I'm STROKE again by misfortune and hoping to get aid.

    by: Oracle SQL Data model; 3.1.1.703 in 64 Bit version

    First matrix DDL are not generated. Same situation as in Re: DDL generation does not.

    I close SDM and reopen it, most of the menus have disappeared. According to another post SQLDeveloper Data Modeler corrupted - no option to open a design , it can help to remove all the files in the file system < version number >.

    But
    1. I didn't wan't to delete all these files. Obviously SDM Store there preferences, etc., he don't want to waste all that time each this bug hits (see 2)
    2. as this seems to be a very common error - happens to me the third time, each time in a row that I use SDM - it should be, are a more specific solution for this error.

    If this file is exactly causing the error with the missing FILE > OPEN MENU and everything what another menu corruption?

    Here I give you all the content in the path:

    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\content.txt
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\.issplash
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.datamodeler
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.audit.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.ceditor.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.db.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.diffmerge.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.gallery.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.help.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.importexport.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.indexing.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.inspector.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.log.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.navigator.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.peek.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.persistence.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.quickdiff.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.replace.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.runner.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.vfs.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.vhv.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.webbrowser.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ideimpl.apple.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ideimpl.indexing-migrator.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.javacore.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.jdeveloper.db.connection.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.jdeveloper.history.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.jdeveloper.subversion.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.jdeveloper.vcs.11.1.1.4.37.59.48
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\oracle.javatools.cache
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.datamodeler\ide.properties
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.datamodeler\preferences.xml
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.datamodeler\product-preferences.xml
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.11.1.1.4.37.59.48\.oracle_javatools_msgdlg.properties
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.11.1.1.4.37.59.48\dtcache.xml
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.11.1.1.4.37.59.48\Editing.layout
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.11.1.1.4.37.59.48\settings.xml
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.ide.11.1.1.4.37.59.48\windowinglayout.xml
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.jdeveloper.subversion.11.1.1.4.37.59.48\auth
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.jdeveloper.subversion.11.1.1.4.37.59.48\config
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.jdeveloper.subversion.11.1.1.4.37.59.48\preferences.xml
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.jdeveloper.subversion.11.1.1.4.37.59.48\README.txt
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.jdeveloper.subversion.11.1.1.4.37.59.48\repositories.xml
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.jdeveloper.subversion.11.1.1.4.37.59.48\servers
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.jdeveloper.subversion.11.1.1.4.37.59.48\vcs.log
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.jdeveloper.subversion.11.1.1.4.37.59.48\auth\svn.simple
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.jdeveloper.subversion.11.1.1.4.37.59.48\auth\svn.simple\154365ece4d08699db0df8ef0c7235ea
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\o.jdeveloper.vcs.11.1.1.4.37.59.48\preferences.xml
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\oracle.javatools.cache\00000000
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\oracle.javatools.cache\00000000\00000000.jdb
    C:\Users\thisUser\AppData\Roaming\Oracle SQL Developer data Modeler\system3.1.1.703\oracle.javatools.cache\00000000\je.lck


    Thank you

    Edited by: LPNO on 24.05.2012 12:58

    So I guess that
    * Use when not TORTOISE SVN to work with SDM intergrated SDM - SVM tool

    No problem to use it if it is in the same SVN version 1.6 of the customer. If you want to do it using other tools, then follow Re: cannot use directory already versioned
    Otherwise, we recommend Data Modeler to be used for the validation, update and merge operations. Particularly early stages for the design to enter the version control repository.

    * Must not order a TRUNK in a no working directory blank.

    The best scenario is to have 'types of system data' directory and the design itself in separate directories in the repository or in separate directories in the local file system. For local files:
    -C:\tmp\21\system_data_types - here are types.xml, defaultRDBMSSites.xml, defaultdomains.xml, dr_custom_scripts.xml
    -C:\tmp\21\FICO_Model - here you can save design - FICO_Model_V20.dmd file and directory of design FICO_Model_V20

    Philippe

  • 4.0 generation of DDL EA3 lost trigger code formatting


    Hello

    I'm using DM 4.0.0.825.

    In the physical model of a table, I added a plsql code in the body of the trigger. The code has been formatted. When you generate the DDL of the table using the DOF preview, the formatting is partially missing.

    Example in trigger's body:

    Start

    /*

    || Trigger is activated?

    */

    If cb_trigger_is_enabled ('CBS' $$ plsql_unit)

    then

    If: new.content_clob is not null

    then

    If sf_ctr_chk_html_ok(:new.content_clob) = ' don't

    then

    raise_application_error (-20000, 'CBS-00208 #1' |: new.pide_id |) '#2' || (: new.csrt_id);

    end if;

    end if;

    end if;

    end;

    Occur in the DOF Preview:

    CREATE OR REPLACE TRIGGER CNTT_BIR BEFORE

    INSERT THE CONTENT FOR EACH START OF LINE

    /*

    || Trigger is activated?

    */

    IF cb_trigger_is_enabled ('CBS' $$ plsql_unit) SO if: new.content_clob IS NOT NULL THEN if sf_ctr_chk_html_ok(:new.content_clob) = ' only THEN raise_application_error ("-20000, ' CBS-00208 #1")

    || : new.pide_id

    || « #2 »

    || (: new.csrt_id);

    END IF;

    END IF;

    END IF;

    END;

    The plsql formatting should be preserved.

    Joop

    Hi Joop,

    This is because the SQL Developer trainer has reformatted the statement.

    If you unset using SQL Developer trainer option in the preferences of Modeler/DDL Data your formatting must be preserved.

    David

  • SQL datamodeler: generation of DDL

    Hello
    Can someone explain the difference between the interactive DOF, advanced and advanced CL DDL?
    best regards Erik

    Erik,

    they should do the same job, the gap is explained at the beginning of scripts (see below) - interactive c. command line parameters. The second option is oriented to be run by other tools.

    Best regards
    Philippe

    -The advanced ODM of script with the support of
    -interactive (SQL/Plus or SQLDeveloper)
    -settings of the input parameters for:
    -starting stage, off stage, log file and the level of logging (1,2 or 3)

    =========================

    -The advanced ODM of script with the support of
    -the command line (SQL/Plus only)
    -settings of the input parameters for:
    -starting stage, off stage, log file and the level of logging (1,2 or 3)

    -The script can be executed as follows (all parameters are mandatory):
    --
    -sqlplus user/passw@name @script_name start_step stop_st log_file log_level
    --
    -Examples:
    --
    -sqlplus scott/tiger@orcl @e:\adv_script.sql 0 e:\adv_script.log 0 2
    --

  • Error in DDL generation

    I created a relational model with a few tables and FK between them.

    When I generate the DDL for the previous model, I get a few bad results:

    (1) DOF for the schema is or even which created tools > Preferences > Data Modeler > DOF > 'include the schema in the DDL' is checked

    My model contains a schema called power

    (2) the DOF contain lines like

    -ERROR: Invalid view V_Difficulty

    ALTER VIEW Food.V_Difficulty ADD CONSTRAINT Difficulty_PKv1 PRIMARY KEY (DifficultyId) DISABLE;

    When there is not a prior statement of 'create view' to: Food.V_Difficulty in the DDL script generated by the SQL Data Modeler.

    I try to remove all theses view the relational model and save the drawing, but when you reopen the design, these views will appear again.

    There is only one view named v_tablename for each table in the relational model. I created directly these views. Maybe I chose an option about a wizard who create them, but I don't remember.

    (3) for the main/master table of my relational model, the DDL contains a trigger with a few columns added that as I have not created directly

    In addition, the trigger is created in 'emp2' when I have no table named emp2 on my model!

    CREATE OR REPLACE TRIGGER Food.Recipe_JNtrg

    AFTER

    INSERT OR

    UPDATE OR

    DELETE ON emp2 for each line

    Declare

    REC Food.Recipe_JN%ROWTYPE;

    Food.Recipe_JN%ROWTYPE empty;

    BEGIN

    REC: = empty;

    IF THE INSERT OR UPDATE CAN

    recomm. Chutney: =: NEW. Chutney;

    ...

    recomm. JN_DATETIME: = SYSDATE;

    recomm. JN_ORACLE_USER: = SYS_CONTEXT ('USERENV', "SESSION_USER");

    recomm. JN_APPLN: IS SYS_CONTEXT ('USERENV', 'MODULE');.

    recomm. JN_SESSION: = SYS_CONTEXT ('USERENV', 'SESSIONID');

    IF THE INSERTION

    recomm. JN_OPERATION: = 'INS ';

    ELSIF UPDATE THEN

    recomm. JN_OPERATION: = 'UPD '.

    END IF;

    ELSIF DELETION THEN

    recomm. Chutney: =: OLD. Chutney;

    ...

    recomm. JN_DATETIME: = SYSDATE;

    recomm. JN_ORACLE_USER: = SYS_CONTEXT ('USERENV', "SESSION_USER");

    recomm. JN_APPLN: IS SYS_CONTEXT ('USERENV', 'MODULE');.

    recomm. JN_SESSION: = SYS_CONTEXT ('USERENV', 'SESSIONID');

    recomm. JN_OPERATION: = 'DEL ';

    END IF;

    INSERT into Food.Recipe_JN VALUES rec;

    END;

    /

    I am writing this question after that I tried, without success, other operations like create a new template and copy table-table of the old model to the new model.

    SQL Developer Data Model Version 4.1.1.888

    OS Win7 64 bit

    This is the version 4.1 a stable version?

    Isaac

    Hi Isaac,.

    (1) I have the physical models, right click and select new. SQL Data model the fill with data, but users, appear as MDSYS and Public (I think because the predefined structures that SQL Data Modeler created: MDSYS.) SDO_GEOMETRY and XMLTYPE) and not my food scheme

    You must right-click on the users node and select new.  Then set its name to food and its Implements schema property to refer to the schema of your food.

    (3) there is a way to remove these rules or only apply them in the generation of DDL?

    During DDL generation, on the generation of DDL Options Panel, you can select the 'Of include Scripts Table DDL' tab and make sure that the insert of Scripts checkbox is disabled for all tables.

    David

  • 11g: eclipselink.ddl - generation ignores @JoinTable

    Hello

    I have two entities with @ManyToMany relationship between them
    @Entity
    public class EntityA implements Serializable {
        ....
        @ManyToMany(mappedBy = "entityAList")
        @JoinTable(name = "MY_A_B_JOIN_TABLE", 
                   joinColumns = { @JoinColumn(name = "A_ID") } , 
                   inverseJoinColumns = { @JoinColumn(name = "B_ID") } )
        private List<EntityB> entityBList = new ArrayList();
        ....
    }
    
    @Entity
    public class EntityB implements Serializable {
        ....
        @ManyToMany
        private List<EntityA> entityAList;
        ....
    }
    And I turned on the generation of DDL in persistence.xml
      ....
          <property name="eclipselink.ddl-generation" value="drop-and-create-tables"/>
          <property name="eclipselink.ddl-generation.output-mode" value="database"/>
    ....
    When I run the project, eclipselink seems to ignore the annotation @JoinTable and tries to create the join table using the default names (ENTITYA_ENTITYB, entityAList_ID, entityBList_ID) naming convention.
    What I have to configure something else for eclipselink use my configuration from join table, or is this a bug?

    Thank you
    Pedja

    Hello

    The joinTable must be set to the side owner of the relationship, in this case in EntityB on entityAList.

    Best regards
    Chris

  • Export file DDL in SQL Developer Data Modeler

    I export my last project of relational model of the DDL weeks in hopes of getting a quick and precise way to create my 17 tables. In the relational model, Cust_ID is the PK yet there is nothing indicating it in the script that is created from the export file DDL.  That's what he created.  Now, when I right click on the customer table in the view of the relational model and then choose Preview DDL, it adds the line of alter table. But when I do this for most of the opther whose phones table tables in the image below, it's just the fields, no PK or PK info. How can I get the PK and FK stand? Thank you, Peter

    CREATE THE customer TABLE

    (

    Cust_id INTEGER NOT NULL,

    Name VARCHAR2 (128).

    Address VARCHAR2 (128 CHAR)

    ) ;

    ALTER TABLE customer ADD CONSTRAINT Customer_PK PRIMARY KEY (Cust_ID);     <-this is displayed in the preview of the DOF, not export file DDL. The telephone table does not show the constraints or keys in each view. Even with almost all tables.

    That's what I have for phones

    CREATE TABLE phones

    (

    Phone_ID INTEGER NOT NULL,

    Phone_Type NVARCHAR2 (10),

    Phone_Number TANK (14),

    Customer_Cust_ID INTEGER NOT NULL

    ) ;

    pkfk.PNG

    Hi Peter,.

    A couple of points to check for definitions of key primary and missing foreign key:

    1. the relational model for the primary keys and foreign keys dialogs have both checkboxes 'Generate in DDL', which are normally set.  Make sure they are always defined.

    2. When you make a DDL generation, on the generation of DDL Options screen, select the PK tabs and UK and foreign key constraints and check the boxes 'Selected' for relevant pharmacokinetics and the FKs are defined.  (These settings are remembered from one generation of DDL to the other, and an overview of the DDL will normally use the same parameters as the most recent generation of DDL).

    What Data Modeler version do you use?

    David

  • Help for the dialog window "Table DDL Transformation Scripts"

    Hello world

    I'm trying to understand how to use transformation scripts. the Fund on the dialog window does not work. Is there a document describing the meaning of each of the Visual controls in this dialog box?

    In particular, I'm looking to create my own script attached to "create an after. Also plays with the 'empty' supplied script I found it's result appear if build up in the DDL result appears whenever I press the button additional Test line:

    Sincerely

    Alek

    Hi Alek,

    Thanks for reporting the problem with the generation of DDL to test. Otherwise, you can look here for more information user Oracle SQL Developer Data Modeler 4.1 - DDL generation using transformation scripts

    Philippe

  • Generate the DDL

    During the generation of DDL, are we suppose to select the PUBLIC and MDSYS under assigned users.

    Why they are listed, and when we're supposed to select.

    Thanks in advance.

    Kind regards

    Zafar

    Hi zak,.

    These DDL generation options are important if you have associated objects (for example, Tables or Types structured) with PUBLIC or MDSYS users in your physical model.

    If you expand these nodes in the dialog generation DDL, it will show the objects that have been associated with these users and allow you to select whether to include these items in the generation of DDL.

    Kind regards

    David

  • Dimensions of construction through the tree of Peoplesoft Manager

    Anyone has examples of query on how to get Peoplesoft Manager tree tables in the proper format or the other parent/child or generation to build dimensions? Or did the Erpi adapter in MDF means?

    ERPi (FDMEE) should be able to connect to Peoplesoft version and extract the information.
    I doubt that you will find many queries for you give exactly what you need.

    See you soon

    John
    http://John-Goodwin.blogspot.com/

  • Scale DDL not generated on the DIGITAL areas (3,1 PROD)

    When generating DDL from a complete model imported designer 9i, no scale is generated for both NUMBERS. For VARCHAR2 it doesn't go very well.

    Example:
    Attribute logic my_variable of MY_TYPE field, which is NUMERIC (10).

    Result of the generation of DDL regular:
    MY_VARIABLE NUMBER

    When you change the type in logic and relational model of logical numeric, scale of 10, the generated result is exactly the same:
    MY_VARIABLE NUMBER

    I tried to close the project you and SQL Modeler also closed, but the problem persists.

    How do I get this working, is there an another workaround?

    Published by: user1862903 on February 27, 2012 11:49

    Hello

    I logged a bug about these problems with the importation of Numeric and Timestamp data types.

    David

  • Data Modeler - compare models and DDL file

    I was the generation of DDL files by importing data dictionary. In the window to compare the models, the orange triangles with exclamation points show tables that are somehow different in the database and my data model.

    It would be a very useful feature, if she did not notice the type of information that never goes to the database. For example I used the Notes field and the table Types, and comparison feature shows that this information is missing in the database. In other words, it shows the exclamation points in each table, even if I had changed one table in my model.

    Is there a reason to make it work like that? Or is it going to be fixed in the future?

    Therefore the Data Modeler has not noticed that the sequence had changed

    DDL for new sequences is generated only - no. ALTER statements. Yet changes in the database can be merged into a physical model.
    I logged a bug for this.

    Philippe

  • Automate the Build Dimension attribute

    This may be a simple. Is it possible to automate the generation of a dimension of the attribute? I don't want you must manually add members in the parent of the size of the award. But do not know if I can use a rule to load do. Also, maybe there is problem with the contour of the parent liaison.

    Thoughts?

    If your dimension of the attribute does not have a hierarchy, you can generate during the build of the dimension of the basic members. Just tag as an attribute column (the size of the attribute must be created first and associate member in the sketch-based)

    If you want to create a hierarchy in the dimension of the attribute, then it needs it's rule own load with the hierarchy.

Maybe you are looking for