Recent changes to feature-requests

#25 add correctly to Maven

2013-11-04T10:17:40.827000Z

Hi,

That doesn't look very simple to me :) 18 pages of instructions is a bit much.

However my opinion of maven has always been the same. I have no objection to other people who find josql useful adding it to whatever maven repositories they wish. I don't use maven myself so I have no use for this and don't have the time to spend learning about what it all means.

But if you need josql adding please feel free to do it yourself.

Gary

add correctly to Maven

2013-11-04T09:49:48.667000Z

Could you please add the latest stable version to maven, with sources, javadoc etc. ?

I want to be able to refer to it from an open-source project that is managed by maven.

Here is a simple way to do it:
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide

Add a maxrow variable to Query.execute

2012-07-31T22:29:25Z

Understand this is outside the basic SQL context, but since I see a major usage of JoSQL being to answer AJAX based "autofill" queries [LIKE 'XXX%'], it would be awesome to have some way to limit the query to the first X number of rows that meet the query results. That should really help on those "LIKE" query's performance!

automatically assign allias

2012-03-15T11:24:59Z

when a select expression doesn't have an allias specified then it will be null.
For example:
SELECT count(fieldName) as count, fieldName FROM clazz GROUP BY fieldName LIMIT 1,1
parsing this query and using the getColumn methods will get me an ArrayList with two SelectExpressions with the following alliases:
count
null.
I'd like to see here something like:
count, fieldName
Or
count, column2
Or anything OTHER than null.
There is no way of getting the fieldName from the query other than substringing the toString() result (which is a horrible idea snice it could change at any given time)

Support Accessor using Map's name value pair

2012-03-05T05:33:47Z

Currently, the accessor is based on Java Bean convention getter. Is it possible to have the accessor work with Map's name value pair without using Bean? This is to avoid generating Java Bean class from the data set. I have different kinds of data set and each data set uses it's own attribute/value pairs. To be able to use JoSQL, I have to create/generate a Java Bean class for each data set.

For each data set to search via JoSQL:
Current: List<MyDataObject>
Wanted: List<Map<String, String>> (So far, I am only interested in string values.)

I could use in memory DB like H2 and dynamically generate DB schema based on attributes. But with JoSQL, I cannot create Java Bean class at runtime.

Is this something worth to consider? Or is there already a way to do this? I just started to look at JoSQL and plan to use it in our project. It's a great fit so far since we only use basic query and the performance is very good: under 1s query for 1M objects.

Thanks in advance!
Bo

syntax error with count(*)

2011-03-29T14:57:52Z

JoSQL parsed:

select count(field) from SomeType where 1 = 1

But gave a syntax error at the star for

select count(*) from SomeType where 1 = 1

varargs custom functions

2011-03-28T10:27:00Z

For formatting (concat) different properties in a query we created a new custom function like:

public String format(String format, Object... args) {
StringBuilder sb = new StringBuilder();
Formatter formatter = new Formatter(sb);
formatter.format(format, args);

return sb.toString();
}

The class was registered by the Query instance but the method was not found. I guess because of the varargs in the method signature.
It would be a nice and very useful feature to have it in JoSQL.

Access array element

2011-03-11T18:10:19Z

I would like to see accessors that can index an element from an array. Such as:

select myarray[2]

perhaps some additional features like

select myarray[*]
or select [*] myarray

to return all the array elements, similar to collections.

I would be willing to tackle this myself, but need a little implementation guidance: I have already added a few simple additions to JoSQL such as bit manipulation operators.

Support classic bean access

2010-11-29T14:13:54Z

By allowing the old style bean access method Object get(String) with the attribute name as parameter, a wide range of interesting uses of JoSQL opens up. In my case, this make it possible to use the JMS selector syntax to accept and reject JMS messages in a post-processing step.

The attached file contains an added Getter helper class (BeanMethod) and an updated Getter.java that fixes this. The changes are minimal and for me the benefits in flexibility is very large.

Improve Documentation

2009-12-09T10:33:58Z

Hi,
Please could you improve documentation arounf custom function handlers. Specifically I can't get enough info from the existing documentation to figure out how to allow a query to call a method in a custom object.
For example using Collection ConcurrentHashMap<String, Order>

and String sqlStatement = "Select * from xxx.Order where " +
" getData('basket') like 'AAA%' and "
+ " getData('client') like 'AAA%'";
a query parse exception is thrown....