PgMDD is on the way to Unicode support

Our development team spent a lot of sleepless nights trying to make PgMDD Unicode friendly. Well, it’s almost done… at least we can show some screenshots without a twinge of conscience.

Unicode is almost here

PS For those smart guys who understand Hebrew: don’t be afraid. That’s just because PC on screenshot has not RTL script support. 😉

Advertisements

Database Designer for PostgreSQL 1.3.2 released

Support for OpenSSL 1.0c and PostgreSQL 9.0.2 libraries added. Error logging improved. Minor bugs are fixed.

You’re welcome to download the latest release from our website at:
http://microolap.com/products/database/postgresql-designer/download/

Full changelog:

[!] Error logging improved
[!] OpenSSL 1.0c used
[*] Inherited constraints excluded by reverse engineering if not redeclared locally in children
[*] Reverse Engineering progress indication improved
[-] “Cast error occurs in New Database Wizard if Connection Limit is higher then 0” bug fixed
[-] “Reverse Engineering failed if table has dropped columns and constraints built on columns at the end of the table” bug fixed
[-] “Trigger time loaded incorrectly from file” bug fixed

Please don’t hesitate to ask any questions or report bugs with our Support Ticketing system available at
http://www.microolap.com/support/

Database Designer for PostgreSQL 1.3.2 Beta available

Support for OpenSSL 1.0c and PostgreSQL 9.0.2 libraries added. Error logging improved.

Attention should be paid to specific PostgreSQL 9.0.2 features testing especially SSL encryption support.

You’re welcome to download the Database Designer for PostgreSQL 1.3.2 Beta right now at:
http://microolap.com/products/database/postgresql-designer/download/

Please don’t hesitate to ask any questions or report bugs with our Support Ticketing system available at
http://www.microolap.com/support/

The PgMDD-1.3.0 had taken off

- Tower, PgMDD-1.3.0 at runway PG9 is ready for departure. Over.
- PgMDD-1.3.0, cleared for take off runway PG9, 
climb and maintain PgSQL 9.x support, 
remain on runway heading until you have contacted 
the controller on the departure frequency, good day.

- PgMDD-1.3.0, cleared for take off runway PG9.
- PgMDD-1.3.0 cleared for take off runway PG9, good day tower.

- All checks complete, power up.
- Power to 70%.
- Indicators checked.
- Checked.

- Beta1!
- Rotate!

- Beta2!
- Positive rate.

- Beta3!
- Gear up. Release!
- Gear up and locked, retract flaps to 2 degrees.

Ladies and gentlemen, this is your captain speaking. On behalf of the flight crew, let me welcome you aboard PgMDD v1.3.0. In this flight you may enjoy such features:

The cabin crew is at your service. Please don’t hesitate to ask any questions or report bugs. I’ll talk to you again later. Until then, sit back, relax and enjoy the rest of the flight with the MicroOLAP Database Designer – world most advanced ER-designer for PostgreSQL – the most advanced RDBMS in the Universe.

PgMDD v1.3.0-beta3 is available

MicroOLAP Database Designer for PostgreSQL aka PgMDD v1.3.0-Beta3 is already available for downloading.

It is supposed to be the last beta, so please test it as thoroughly as possible. The main features of the upcoming v1.3.0 are:

Stay tuned for details.

Please don’t hesitate to ask any questions or report bugs with MicroOLAP’s Support Ticketing system.

1-to-1 relationship in PostgreSQL

Today I received mail from one of my clients:

I am using MicroOLAP Database Designer to develop a ERD for a PostGIS database. In my opinion one drawback to PgMDD is the lack of an explicit cardinality determination on the relationship. It is not obvious how to declare two tables in a IS_A relationship (1:1) and there is no sufficient explanation in the help section.
Would you be so kind as to support me with some information how I can determine a 1:1 cardinality on a relation.


I don’t want to discuss the reasons why one may need 1-to-1 relationship design. I just want to propose solution for it. Trick is simple, I suppose. All we need is to add unique constraint (or index) to child table.

Let’s imagine we have two tables Users and UserProfiles:

CREATE TABLE "UserProfiles" (
        "UProfileID" SERIAL NOT NULL,
...
        PRIMARY KEY("UProfileID")
);

CREATE TABLE "Users" (
        "UID" SERIAL NOT NULL,
        "UProfileID" int4 DEFAULT 0,
...
        PRIMARY KEY("UID"),
        UNIQUE("UProfileID"),
        FOREIGN KEY ("UProfileID"REFERENCES "Users"("UProfileID")
);

That’s all. Opposite case where referenced and referencing table are changed did the trick either.

Beta of PgMDD v1.3.0 is available

MicroOLAP Database Designer for PostgreSQL aka PgMDD v1.3.0-Beta is already available for downloading.

As you can see this is new minor release. It is timed to coincide with the PostgreSQL 9.0 release. The main features of the upcoming v1.3.0 are:

Stay tuned for details.

Please don’t hesitate to ask any questions or report bugs with MicroOLAP’s Support Ticketing system.