We've fixed the backup issue in case the schema name is set in the connection string or in the PgSqlDump properties.
As I can understand, you are not experiencing any problems with restoring databases when no schema name is set. Am I correct?
As for 'running on the same machine', it was meant, did you try executing both the test project and your application on the same machine, or, e.g., the test application was run on the development PC only, whereas the real application was used on the production server? In latter case, it was possible that some system settings affect interoperations with the database.
We will consider backing up table privileges, and post here when this feature is implemented. At the moment, such functionality is not available.
PgSqlDump and pgAdmin III
I appreciate the support for this issue.
The test project you sent and my application were both run in the same machine. The only issue I had was when the schema was set in the connection string. There is no problem if the schema is defined in pgSqlDump schema property.
Best regards,
Jorge Maldonado
The test project you sent and my application were both run in the same machine. The only issue I had was when the schema was set in the connection string. There is no problem if the schema is defined in pgSqlDump schema property.
Best regards,
Jorge Maldonado
-
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
We have released the new 5.10.121 build of dotConnect for PostgreSQL where the backup issue with the specified schema name is fixed. The new build can be downloaded from
http://www.devart.com/dotconnect/postgr ... nload.html
(the trial version) or from Registered Users' Area (for users with active subscription only):
http://secure.devart.com/
For the detailed information about the fixes and improvements available in dotConnect for PostgreSQL 5.10.121, please refer to
http://www.devart.com/forums/viewtopic.php?t=20473
http://www.devart.com/dotconnect/postgr ... nload.html
(the trial version) or from Registered Users' Area (for users with active subscription only):
http://secure.devart.com/
For the detailed information about the fixes and improvements available in dotConnect for PostgreSQL 5.10.121, please refer to
http://www.devart.com/forums/viewtopic.php?t=20473
-
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
We have implemented support for tablespaces in PgSqlDump (i.e., they can now be included into the table definition script). To enable this option, please set the IncludeTablespace property of PgSqlDump to true.
This feature is available in the new 5.10.135 build of dotConnect for PostgreSQL. This new build can be downloaded from
http://www.devart.com/dotconnect/postgr ... nload.html
(the trial version) or from Registered Users' Area (for users with active subscription only):
http://secure.devart.com/
For the detailed information about the fixes and improvements available in the latest build, please refer to
http://www.devart.com/forums/viewtopic.php?t=20709
This feature is available in the new 5.10.135 build of dotConnect for PostgreSQL. This new build can be downloaded from
http://www.devart.com/dotconnect/postgr ... nload.html
(the trial version) or from Registered Users' Area (for users with active subscription only):
http://secure.devart.com/
For the detailed information about the fixes and improvements available in the latest build, please refer to
http://www.devart.com/forums/viewtopic.php?t=20709