Fabian
|
| Posted: 08/23/2002, 6:00 AM |
|
Hello there,
I'm experiencing a very weird behaviour evaluating CCS during the design phase.
While connecting to Oracle via the ODBC driver everything is allright, when connecting to PostgreSQL via ODBC also (the connection is okay, can use also PGAdmin on same design PC) when I'd expect to see all the tables on teh DB I only see a couple of them. Also, If I use one of these, CCS is unable to identify the PK of the interested table (yes, it exists) so, making it selected by hand and finishing the project I have as a result a couple of corrupted pages which aren't deletable nor editable.
I'm on the following versions: CCS 1.0.7, PERL 5 and Templates, PG 7.2.1, ODBC PG driver 7.02.00.01, WinXP Home, PG Server SS5/Solaris 2.6.
I'm I doing something wrong ?
Many thanks.
Fabian.
|
|
|
 |
Nicole
|
| Posted: 08/24/2002, 2:30 AM |
|
Fabian,
do you use trial or registered CCS version?
I suggest you to contact CCS support about this problem.
The link to submit the request is: http://support.codecharge.com/support_new.asp
|
|
|
|
Fabian
|
| Posted: 08/24/2002, 2:43 AM |
|
Hi Nicole,
Definitively, I'm trying to understand if CCS is the product to suit my needs, so I'm using the trial.
But, if everything's allright with Oracle, how can the connection go wrong ONLY with PostgreSQL via ODBC?
Am I entitled to such a shallow suppport level even when trying it up ?
Many thanks.
Fabian.
|
|
|
|
Fabian
|
| Posted: 08/24/2002, 2:43 AM |
|
Hi Nicole,
I'm still using the trial version to understand how it works down PG.
Looks like there incompatibilites ONLY with PG since Oracle goes well so, can it really depend on the fact that I'm using a trial ?
How Can I contact Support for a trial version ?
Many thanks.
Fabian.
|
|
|
|
Nicole
|
| Posted: 08/26/2002, 11:35 PM |
|
Fabian,
Of course you can contact CCS support while using trial version. I think it is better to contact them about this problem.
Also are you able to see all tables listed when using different CCS examples with lets say Access db?
|
|
|
|
Jim
|
| Posted: 11/02/2002, 8:39 PM |
|
I'm finding other problems with scripts generated for perl/psql. It's not handling quoting very well. It ends up generating code shown below, which of course isn't going to work. The odd thing is, it doesn't always do it - it only does it on insert/update/delete sql. Plain selects don't have that problem. I was really excited to find a product that generated perl code, AND worked with Postgres, but this is a pretty serious bug, since it means I now have to hand debug any generated code...
$SQL = "INSERT INTO "categories" ("
. ""cat""
. ") VALUES ("
. $self->ToSQL($self->{cat}->GetDBValue(), $self->{cat}->{DataType})
. ")";
|
|
|
|
Jim
|
| Posted: 11/05/2002, 8:48 PM |
|
I found a workaround for the problem I was having with postgres. I'd only do this if you don't have any odd field names (like with spaces in them). Edit the postgres.xml file, and change the field delimiters to just '', instead of '"'. It's been working great for me since then, except for the weird disappearing, reappearing menu stuff.
Support has a fix to download for the quoting problem, but it introduces other problems, so I'm sticking with the postgres.xml tweak for now. Hopefully it won't cause othe problems later.
|
|
|
|
|
