Welcome to ModelRight Database Design Tool - Database Modeling Done Right Sign in | Join | Help
in

PGSQL validation error question

Last post 09-04-2009, 2:19 PM by modelright. 1 replies.
Sort Posts: Previous Next
  •  09-04-2009, 1:01 PM 1317

    PGSQL validation error question

    I am running the trial version of ModelRight Pro for possible use in a Postgresql project and am getting the following validation errors when running the Validate... menu choice against a reverse-engineered model:

     Error: :  Objects With No Standard Names:  <default>:  Name contains illegal characters
    Error: :  Objects With No Standard Names:  v_combined_summary_data.pledge end date:  Name contains illegal characters
    Error: :  Objects With No Standard Names:  v_combined_summary_data.pledged gift amount:  Name contains illegal characters
    Error: :  Objects With No Standard Names:  v_combined_summary_data.non-pledge gift amount:  Name contains illegal characters

    There are a number of instances, at least two of which seem to pertain to <default> values not a part of the reversed schema. It doesn't seem to like the spaces in the column names on everything else (since removing them removes the error) which may not be great practice but I don't think is actually an error (since it works just fine in the original database). Just wondering if this is intentional behavior, and if there is a way to remove the error for the <default>s. I realize this is pretty minor and easily worked around, so is more informational on my part in evaluating the software... thanks

  •  09-04-2009, 2:19 PM 1318 in reply to 1317

    Re: PGSQL validation error question

    Space, tab, etc chars are usually illegal to be used in object names unless the names are quoted. That probably is the case for your databases. For most databases, space will be an illegal name to be used for object names.

    In your model, the "Allow special characters" should be turned on; and if turned on then you should not see the error/warning above.

    We will fix it so it won't flag such naming errors when "Allow special characters" is on.

    For now, you can uncheck the validation option for "Objects with no standard names".

    Hope this helps. 

     

     

     


    ModelRight Evangelist