Introduction

The project pgDesigner was designed to provide a graphical environment, open-source and non-commercial, as an aid for the design and creation of database PostgreSQL. In effect on the market similar applications exist, and certainly more advanced pgDesigner, but are often commercial, non-free or subject to restrictive licensing.

pgDesigner was born after a long and unsuccessful search network of similar programs, and also for my personal bet, because at that I heard about a new language, Gambas, which is also open source, and that seems to promise much good as an alternative to Visual Basic in a Linux environment, the thing I was so intrigued by then it will test the real ability and potential, then I asked myself, why not combine the two?

As evidenced by its author (Benoit Misinini) on the official website of Gambas, this language does not want to be absolutely a copy of the Windows environment, and from what I have seen is actually the case. Gambas, while maintaining the basic structure of the Basic language, seems to be willing to fix many bugs and shortcomings of its antagonist, while preserving snellezza and power, in addition to the fact that this was born and works under Linux.

After osanna this language, we speak of this manual: pgDesigner.

Currently the program has been in a sufficiently functional, with the necessary groundwork for developing projects for the creation of database to PostgreSQL. The application is based essentially on a single environment (SDI), with which it is possible to design the structure of an archive.

The development of PostgreSQL is constantly changing, especially in recent times where they are well-known RDBMS such as Oracle and DB2, it is possible that some new implementations have not yet been added to the program, but not desperate ...

The interface is very simple and is described in subsequent chapters.

NOTE: This documentation makes reference to the current version of pgDesigner, which currently is 1.1.0 and it is possible that some references or images differ later. Normally documentation should follow a step-by-step evolution of the software, but this is possible only in environments medium / large, the number of people is greater than one; unfortunately currently the only developer, tester and manager of the documentation is a only, and this being a non-commercial, developed in the limited time available, in conditions very significant parallel processes.

I thank all those who helped with translations, ideas, advice and various aid.

I invite everyone to contribute to the improvement of the program by providing advice or suggestions.

I am also willing to consider partnerships, both for the environment and development tests, which for the documentation.

Luigi Carlotto
Roma - Italy