Holidays came suddenly. I know we’re little bit late with Christmas presents, but who cares anyway!
welcome to use “Christmas” coupon code till January 14 for 20% discount on any product from MicroOLAP Technologies including the most robust Database Designer for PostgreSQL and PostgresDAC component suite.
From all of us at
MicroOLAP, we wish you happy holidays and a prosperous new year!
For all blog readers and
@microolap followers! You may use special registration code to extend trial period for MicroOLAP Database Designer for PostgreSQL for two months. Just use in the registration window:
Blog Reader key:
Thank you for using MicroOLAP Database Designer for PostgreSQL!
So, guys! You may follow @microolap on Twitter for the latest updates!
We have ignored this service for too long, but the time has come!
We will use such hashtags:
Our client asked:
I have a script that can be created directly from PgAdmin, but it is not possible to create these scripts in PgMDD.
The function has a simple structure as defined below. The important part, is the return type (TABLE)
CREATE FUNCTION function_name() RETURNS TABLE(column_name_1 integer, column_name_2 character varying)
RETURN QUERY (SELECT id, name FROM customer);
PgMDD does not allow you to to that.
PgMDD doesn’t support ANSI syntax RETURNS TABLE, but you may do this in PostgreSQL way by using OUT parameters.
There is a good article
“Using RETURNS TABLE vs. OUT parameters” by Leo Hsu and Regina Obe describing this approach.
So this function may be defined like this using PgMDD:
FUNCTION column_name_1 OUT integer,
column_name_2 OUT character varying)
RETURN QUERY ( $BODY$ id, name SELECT customer);
Our client asked:
I lost every previously defined connection setup!! (from previous versions of MicroOLAP Database Designer for PostgreSQL)
Yes, since new release of
PgMDD stores all information in Unicode we didn’t implement import of connection data from old ANSI profiles by default. We want to keep them intact.
And now we’ve added import functionality for the
Connection manager. All you need to do to have all your defined connections is:
Click Import button;
As I wrote in my previous
post, we spent a lot of sleepless nights trying to make PgMDD Unicode friendly. And now there is finish line in sight.
Click to enalrge
Ladies and gentlemen, let me introduce you MicroOLAP Database Designer for PostgreSQL v1.8.0-beta.
“Why 1.8?” – one may ask. Yes, indeed. Our last stable release was v1.3.2, so why such a huge leap?
There are two reasons. The first, Unicode support is a milestone for the branch v2.x of the product. Thus half the job is done.
The second, is more tricky. As you probably know
i18n numeronym stands for internationalization (where 18 stands for the number of letters between the first i and last n). And we sincerely believe that the Unicode support is a prerequisite for proper internationalization.
That’s the story!
This morning I opened
Planet PostgreSQL and found that we have a brand new contributor Binod Nepal. In one of his posts Binod presented a sample database of academic institutions, which I found very attractive.
I created this database and then import it to
MicroOLAP Database Designer for PostgreSQL. That’s how visual model of this database looks like.
Academic Sample Database for PostgreSQL
PS. We want to include this model into PgMDD’s sample models shipped with installation, if Binod does not mind.