While I'm learning how to use RoboDemo, I've put together a small RoboDemo movie of how to fix a bug for PostgreSQL Data Source configuration in the ColdFusion MX Administrator.


I discovered the solution on this CFTALK thread, so I can't take credit for this. The problem is that when configuring a PostgreSQL dsn according to the instructions in this TechNote, if you choose a Driver Name field of PostgreSQL, then that will trigger ColdFusion to invoke a handler template of "postgresql.cfm". This handler template is defined in the configuration file neo-query.xml in ColdFusion MX's lib directory.

At one time the ColdFusion MX Administrator was going to provide a PostgreSQL JDBC driver out of the box, and that was partially implemented. However, the postgresql.cfm handler file was never implemented or even created. The result is that after first creating the datasource, when you return to edit it again ColdFusion will recognize the Driver Name of PostgreSQL and attempt to trigger the postgresql.cfm handler. This causes the error:


"File not found: /CFIDE/administrator/datasources/postgresql.cfm The specific sequence of files included or processed is: C:CFusionMXwwwrootCFIDEadministratordatasourcespostgresql.cfm "


The solution in the CFTALK thread shows how to change the handler reference from postgresql.cfm to default.cfm. Then restart ColdFusion MX. You will then be able to edit the datasource correctly.


View RoboDemo of Workaround





Pete Freitag pointed out in a comment that a better solution would be to find the default.cfm then make a copy named postgresql.cfm. That would do it. Thanks Pete!