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 222740 - Refresh Records doesn't work
Summary: Refresh Records doesn't work
Status: RESOLVED WORKSFORME
Alias: None
Product: db
Classification: Unclassified
Component: SQL Editor (show other bugs)
Version: 7.3
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-26 08:39 UTC by medeag
Modified: 2012-11-26 13:44 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description medeag 2012-11-26 08:39:28 UTC
Product Version: NetBeans IDE Dev (Build 201211200002)
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)


from test spec
1. Open SQL editor.
2. Type some query.
3. Run it.
4. Change data outside IDE.
5. Press "Refresh Records" button.

output:
5. Data should be refreshed.

I have run query following query:

select * from my_table;

then updated varchar column value outside of ide using Navicat Lite clicked refresh, but nothing changed, i tried re-run query, still nothing changed, only after i closed opened netbeans record finally changed.
Comment 1 Jaroslav Havlin 2012-11-26 10:49:39 UTC
I tried it several times, but I observed reported error only once. I debugged it and incorrect data were returned from the database, so it seemed that it was not a NetBeans issue.

Can you reproduce the bug constantly?
What database server do you use?
Comment 2 medeag 2012-11-26 11:05:39 UTC
I have tried several times and  I couldn't reproduce it either, so please feel free to close this issue...
Comment 3 Jaroslav Havlin 2012-11-26 13:44:15 UTC
(In reply to comment #2)
> I have tried several times and  I couldn't reproduce it either, so please feel
> free to close this issue...
I cannot reproduce any more. OK, closing for now.
Thank you for reporting.