Instructions for building from source can be found in the documentation. There are source code and binary packages of beta and release candidates, and of the current development code available for testing and evaluation of new features. Note that these builds should be used for testing purposes only , and not for production systems.
It's worth mentioning that the import and diff processes were also improved to support all the mentioned improvements in those objects. The data type configuration widget received a simple improvement which adds a significant reduction in the time spent to configure a data type.
Now, the user can just type the name of the desired data type to be used instead of selecting it by using the mouse. After typing the data type name just hit the tab key to jump to the next field and the data type will be automatically configured. Seems a silly fix but it adds speed when you need to repeatedly create columns in a table, for example.
In the SQL tool, is now possible to drop databases quickly from the databases listing. Previously, there was the need to browse the database first and then drop it. In the database browser widget, the tree items collapse state is saved and restored after any updates requested by the user, improving the overall experience on that module.
In data manipulation form, the sorting operation performed when clicking columns was adjusted. Now, the sorting will be triggered by holding the control key and clicking the desired column, and if the user only clicks a column without holding the control key will cause the entire column to be selected in the grid.
Attending to some requests, pgModeler is now capable of exporting the database model in split SQL files instead of generating a single SQL file representing the entire database. In this export mode, the files are named in such a way to represent the proper order of creation, which means that running the scripts one after another will create the whole database like it was created from a single file. Due to the introduction of a new syntax highlighting configuration file for code snippets configuration , pgModeler will, from now on, create missing configuration files at startup.
This will avoid breaking the tool's execution when it detects the absence of any configuration file. Also, during the copy of these files, pgModeler will enforce the write permission over them to avoid access problems on some systems that store template settings on read-only paths. The command-line interface was patched in such a way that now doesn't crash anymore when performing a diff operation in which a database model is used as input.
Another improvement to the CLI is the introduction of the option --force in the mime type handling operation.
Also, a patch was made in such a way to avoid the usage of option '-platform offscreen' explicitly when calling the application.
Finally, there is a bunch of other new features and bug fixes implemented in almost all parts of the tool which improves stability and reliability. Purchase Purchase an access key and support this project. Source If you want to compile pgModeler by yourself, you can grab the source code from the official repository. Purchase packages. Release: 0. The table below provides links to the location of the files on the primary server only.
These are the canonical release forms of GnuPG. To use them you need to build the binary version from the provided source code. For Unix systems this is the standard way of installing software. Debian, Fedora, RedHat, or Ubuntu which may already come with a directly installable packages.
However, these version may be older so that building from the source is often also a good choice. Some knowledge on how to compile and install software is required. The table lists the different GnuPG packages, followed by required libraries, required tools, optional software, and legacy versions of GnuPG. For end-of-life dates see further down.
0コメント