Thanks for your attention to the wording of the Dialog in the
Connections wizard.
As to your questions about the problems that i was having with the
latest version of rekall, I installed and ran it on a Dell Optiplex 150
GX (Pent 3 1GHZ, 512 Ram) running Fedora Core 3. My home network has 3
machines running Postgres - 2 Win XP Pro machines running 8.03 and 8.1
Beta, and then the Linux machine runs 8.03 built from source. All the
crashes I experienced were related to establishing connections to
Postgres Databases on any of these machines, I would use the wizard and
then enter host and DB info and with out exception the program would
silently exit. It was not always at the same point, and on a couple of
occasions when I restarted the program I found that the Rekall project
File had been created and i could connect with the stored connection info.
I have tried starting Rekall from the command line so as to see what it
leaves when it exits, but it does seem to be a really silent exit. I
have not done any more debugging than that.
As I have said here a couple of times I think that there is a real need
for an Access competitor, which Rekall promises to be - but I think we
already have a number of really excellent GUI DB managers, and to me
Rekall looks more like a Db Manager than Rich Client cum RAD tool for Db
centric applications.
Cheers
Johan Wehtje
John Dean wrote:
Hi Tom
At 03:32 18/10/2005, Tom Lane wrote:
Johan Wehtje <joweht@xxxxxxxxxxx> writes:
> I was more disappointed in the fact that when the Wizard is used to
> build a Database connection to Postgresql the information box text
> informs the user that the "Postgresql is not as fast as MySql, but does
> have support for transactions and Stored Procedures".
> Given that from the 7 series onwards the relative speeds of MySql and
> Postgresql is not something that has a clear and definitive answer, I
> would suggest that the Connection Wizard text is misleading at best.
And I suppose the MySQL boys will be objecting to the second part of the
sentence as soon as MySQL 5.0 goes gold ;-)
I agree with you, as I have already mentioned to Johan. I believe the
user already knows which database engine he/she is going to use and more
than likely he/she is fully aware of the pros and cons, so there is no
need to point them out
regards, tom lane
---
Regards
John Dean,
co-author of Rekall,
the only alternative
to MS Access
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
.
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
