Mined Opinions For API: java.sql
This tab contains all the opinions collected from Stack Overflow about the API. The other tabs present summaries of the opinions using different algorithms.
- I found a very stupid mistake in my app.Instead _java.util.Date_ I used _java.sql.Date_ in my Model class :( Thats why Date field always was null.. details
- 1: So to use less memory we must: use server side cursor behind the scene use resultset open as URL_http://docs.oracle.com/javase/6/docs/api/java/sql/ResultSet.html#CONCUR_READ_ONLY [read-only] and, of course, URL_http://docs.oracle.com/javase/6/docs/api/java/sql/ResultSet.html#TYPE_FORWARD_ONLY [forward-only] ; avoid to load all the cursor in a list (or a CODETERM1 ) but write each row directly on an _output line_, where for output line I mean an output stream or a writer or also a json generator that wraps an output stream or a writer.. details
- 4: I used arrays to cache thinks and to avoid to call getters each iteration.. details
This tab shows statistical summaries of the opinions. The 'Aggregated Sentiment' shows the overall distribution of polarity (positive vs negative) in the opinions. The 'Monthly Trend' shows how the polarity changed over months. The 'Comentioned API' shows other APIs co-reviewed in the same post where java.sql was discussed.
Rating:Chart will be rendered here
Chart will be rendered here
Chart will be rendered here
Summaries the opinions about java.sql using topic modeling.
-
0. output stream writer cursor avoid row open directly side call: 3
- I found a very stupid mistake in my app.Instead _java.util.Date_ I used _java.sql.Date_ in my Model class :( Thats why Date field always was null.. details
- 1: So to use less memory we must: use server side cursor behind the scene use resultset open as read-only and, of course, forward-only ; avoid to load all the cursor in a list (or a JSONArray ) but write each row directly on an _output line_, where for output line I mean an output stream or a writer or also a json generator that wraps an output stream or a writer.. details
- 4: I used arrays to cache thinks and to avoid to call getters each iteration.. details
Summaries of the opinions about java.sql using three algorithms (Textrank, Lexrank and Luhn) adopted from extractive summarization. Each algorithm was used once for the positive opinions and once for the negative opinions.
- Thank you for your question .
- Hope this helps Solution is to use java sql Time instead of java sql Date .
- Thank you for your question .
- Hope this helps Solution is to use java sql Time instead of java sql Date .
- Thank you for your question .
- Hope this helps Solution is to use java sql Time instead of java sql Date .
- I found a very stupid mistake in my app Instead java util Date I used java sql Date in my Model class :( Thats why Date field always was null .
- 1: So to use less memory we must: use server side cursor behind the scene use resultset open as read only and, of course, forward only ; avoid to load all the cursor in a list (or a JSONArray ) but write each row directly on an output line , where for output line I mean an output stream or a writer or also a json generator that wraps an output stream or a writer .
- 4: I used arrays to cache thinks and to avoid to call getters each iteration .
- I found a very stupid mistake in my app Instead java util Date I used java sql Date in my Model class :( Thats why Date field always was null .
- 1: So to use less memory we must: use server side cursor behind the scene use resultset open as read only and, of course, forward only ; avoid to load all the cursor in a list (or a JSONArray ) but write each row directly on an output line , where for output line I mean an output stream or a writer or also a json generator that wraps an output stream or a writer .
- 4: I used arrays to cache thinks and to avoid to call getters each iteration .
- I found a very stupid mistake in my app Instead java util Date I used java sql Date in my Model class :( Thats why Date field always was null .
- 1: So to use less memory we must: use server side cursor behind the scene use resultset open as read only and, of course, forward only ; avoid to load all the cursor in a list (or a JSONArray ) but write each row directly on an output line , where for output line I mean an output stream or a writer or also a json generator that wraps an output stream or a writer .
- 4: I used arrays to cache thinks and to avoid to call getters each iteration .
Summaries of the opinions about java.sql using Opinosis, an abstractive summarizer of opinions..
Summaries of the opinions about java.sql using contrastive viewpoints. Each entry contains a pair of positive and negative sentences that are most likely discussing about similar API features.
Summaries of opinions about based on specific API aspects, such as, performance, usability, etc. The 'Overview' page provides an overview of the aspects detected in the opinions. The 'Trend' page shows the distribution of polarity over time for each aspect. The 'Positive Opinions' page groups positive opinions by the detected aspects. The 'Contrastive By Aspect' page shows paris of contrastive opinions under each aspect (where found).
Onlysentiment:
- Thank you for your question.
- N/A
Usability:
- Hope this helps URL_https://forums.oracle.com/forums/thread.jspa?threadID=83378 [ URL_https://forums.oracle.com/forums/thread.jspa?threadID=83378 ] Solution is to use java.sql.Time instead of java.sql.Date .
- I found a very stupid mistake in my app.Instead _java.util.Date_ I used _java.sql.Date_ in my Model class :( Thats why Date field always was null.
Chart will be rendered here
Chart will be rendered here
-
Onlysentiment: 1
-
general: 1
- Thank you for your question.. details
-
-
Usability: 1
-
general: 1
- Hope this helps URL_https://forums.oracle.com/forums/thread.jspa?threadID=83378 [ URL_https://forums.oracle.com/forums/thread.jspa?threadID=83378 ] Solution is to use java.sql.Time instead of java.sql.Date .. details
-
-
Usability: 3
-
general: 3
- I found a very stupid mistake in my app.Instead _java.util.Date_ I used _java.sql.Date_ in my Model class :( Thats why Date field always was null.. details
- 1: So to use less memory we must: use server side cursor behind the scene use resultset open as URL_http://docs.oracle.com/javase/6/docs/api/java/sql/ResultSet.html#CONCUR_READ_ONLY [read-only] and, of course, URL_http://docs.oracle.com/javase/6/docs/api/java/sql/ResultSet.html#TYPE_FORWARD_ONLY [forward-only] ; avoid to load all the cursor in a list (or a CODETERM1 ) but write each row directly on an _output line_, where for output line I mean an output stream or a writer or also a json generator that wraps an output stream or a writer.. details
- 4: I used arrays to cache thinks and to avoid to call getters each iteration.. details
-