This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 223502 - Different behavior between mysql and postgreSQL in the New Connection Dialog
Summary: Different behavior between mysql and postgreSQL in the New Connection Dialog
Status: VERIFIED DUPLICATE of bug 149489
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 7.3
Hardware: All All
: P4 normal (vote)
Assignee: matthias42
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-07 19:44 UTC by medeag
Modified: 2015-03-03 19:35 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description medeag 2012-12-07 19:44:09 UTC 
Product Version: NetBeans IDE Dev (Build 201212030001)
Java: 1.7.0_10-ea; Java HotSpot(TM) 64-Bit Server VM 23.6-b04
Runtime: Java(TM) SE Runtime Environment 1.7.0_10-ea-b15
System: Mac OS X version 10.7.5 running on x86_64; US-ASCII; ka_GE (nb)

Not sure whether it is bug or not,
when you select posgresql driver in the New Connection dialog the host/port is not automatically populated in the contrast to mysql, where host is automatically localhost and port is 3306
Comment 1 Jaroslav Havlin 2012-12-10 12:37:46 UTC 
(In reply to comment #0)
> Not sure whether it is bug or not,
> when you select posgresql driver in the New Connection dialog the host/port is
> not automatically populated in the contrast to mysql, where host is
> automatically localhost and port is 3306.
This is not a bug, this feature is not currently supported for PostgreSQL.
Marking as enhancement. Thanks for reporting.
Comment 2 matthias42 2015-03-01 17:47:42 UTC 
Closing as duplicate of 149489. The mentioned bug requests a sample for postgresql and this is the difference to mysql which already provides one. So that bug is essentially the same as this one.

*** This bug has been marked as a duplicate of bug 149489 ***
Comment 3 medeag 2015-03-03 19:35:32 UTC 
looks good, thanks