Hello to all!

I've been facing a strange abnormality when trying to connect manifold and postgresql, both are in the server.

Before explaining the problem, here are my system information (server, postgresql and manifold) as well as the steps I did in order to connect the 2 applications.

• Server: Windows Server 2003 Web Edition with SP2
• PostgreSQL: PostGreSQL DB 8.3, running on localhost, port:5432 and username: postgres, password: ****
• Manifold 8.07.0 Enterprise Edition, x32.

By the way, i've got pgadmin that lets me login to postgre, and work with it really well never got any problem using with the postgres.

To connect manifold to postgres i did the following:

• Defined a DSN File, using the ODBC Source Administrator, with the following specification: PostgreSQL ANSI v8.03.02.00 (dll's name is: "PSQLODBC30A.DLL"), also tryed with the Unicode instead of the ASCII and the results where the same. The connection information i used was obtainded by pgadmin server information, the same as the one provided above (second bullet)
• Opened Manifold and went to Tools -> Server console -> 3 dot Button and choosed the dsn file created before, filling in any required information.
• Closed it and went to Tools -> Database Console, where i didn´t need to define any sql connection because manifold detected the PostgreSQL connection defined before, so i just did a refresh and my test table was there.

So the problem is this, if i want to connect to PostgreSQL data base i'm forced to open the Tools -> Server Console before i go to Tools -> Database Console, if i don’t do this i'll get a "can't connect..." message when going to Tools -> Database Console and i need to close and open manifold again.

If I configure a postgresql connection inside the Database Console, it does not work also, only works ifI open theTools -> Server Console before that.

Anybody faced this problem (assuming that i'm not doing anything wrong)?

Yes, I have had the same problem--intermittently. Connects successfully through the database console, but not through the File menu. It was on a VERY slow connection (WiMax connection in Wyoming to the backside of my cable modem in Colorado). I took a laptop downtown to a coffee shop on a different ISP that goes through a different set of routers, and I was able to connect either way (file/open or /link and database console).

I think there are some packet timeout sensitivities in play here, and if a packet times out, one end or the other (Manifold or Postgres) goes into la-la land. It seems to affect the database console less.

I didn't spend too much time troubleshooting the problem other than looking at the Postgres logs because it was a less-than-ideal connection, not something I would use in the real world.

Well now it's working really better now.

However i noticed that i'm not able to successfully use Manifold's "PostGreSQL Data Sotrage Sources()" by going trought File -> Link -> "Something" -> Choosing here "PostGreSQL..." or By going to Tools -> Database Console -> Choosing here "PostGreSQL...".

The only way i "could" make it work was when i 1st open manifold, i'm forced to go to Tools -> Server Console -> dont need to do anything here if i already defined a "PostGreSQL Data Storage Sources()" connection and its parameters.

This required step gives the impression that its the only way that manifold remembers/pass the connection string to other menus where it's needed, because if i dont do it it will keep "forgeting" the connection parameters.

Well in fact to access to postgresql server ill have to close manifold and open again but i cant forget to visit the "Server Console" Menu before thinking about visiting any menu related to retrieve data from the server.

On the other hand i'm able to setup easily a ODBC connection, and it connectes really well with the postgresql server (alt least until now).

So the bottom line is that inside manifold when i need to reach the server instead of using the "PostGreSQL Data Sotrage Sources()" which is getting a bit "buggy" to me i'll choose the "ODBC Data Source ()" and the connection created using the psqlodbc drivers.

By using this connection all is working well :)

I hope the next version of manifold has this postgres issues fixed, it would be a really huge disapointment if they persist. :|

Regards.

I have no problems using the native 'PostgreSQL Data Souce' from Database Console or menu->file->link|import. Server Console asks for ODBC connectors.

For Shared Components it's important that you give access to all the mfd... tables. Have you changed the postgreSQL account since you create the Enterprise Server sharing the very first component? "mfd_root" is created with full rights for the owner only. The owner is the creator. No public access by default.

For Linked Components the same is true for "geometry_ columns", "spacial_ref_sys" and if you have for "MFD_META".

So check permissions in pgadminIII. Don't use the new PostgreSQL feature of group roles, always use a login user. Groups do not function as expected here, a PostGIS problem, not a Manifold problem.

In these case i was working with a test table.

I created a tabe using postgres account and populate it wti some values, and the goal was to access it trought the database console, which was not connecting to the postgres server.

I didnt tryed yet using geoms because of the connection issues.

I'll give it a try now that i have a working connection.

Thanks.

I got these or similar issues now The owner of the database and can connect to the database according to the test function in the dialog creating the connection but an OK in this dialog was immediatly followed by a 'can't connect to the server'. Later I could use this unchanged connection. The breaking of the connection effects QGIS or pgAdminIII opened by the same user in the background the same way! I have not seen this with build 8.0.6. Connections are extreemly slow, much slower than from QGIS with an initial delay of about 30 seconds before the transfer starts.

Export of Drawings with Manifold geometry fails (invalide metrics, MFD_META filled with partly undocumented PROPerties) whereas a later INSERT of objects succeeds in the ordinary table but apparently not in the index table. So the AOI function must fail. I have to take a closer look at this.

Hello Klaus.

From what i've seen I'm not the only one tho have issues related to manifold's native posgresql.

In my case i've not had the opportunity to test the speed performance, but my major problem the fact that manifold does not handle well the connection with posgresql data base (i've described the problem in the 2 posts above).

Im point more to a manifold "thing" and not a baddly connection configuration.

Regards