https://sourceforge.net/p/jsqlparser/feature-requests/Recent changes to feature-requestsenTue, 11 Dec 2012 02:56:54 -0000https://sourceforge.net/p/jsqlparser/feature-requests/_discuss/thread/42d11046/Just pushed the first release built entirely using maven to central (0.8.0). Next release will be 0.8.1. Cheers, RobRob ManningTue, 11 Dec 2012 02:56:54 -0000https://sourceforge.netdec8d00a07c83441588a1fa4dc3982f8cfa64783https://sourceforge.net/p/jsqlparser/feature-requests/6/Make a jdk1.5 compatible buildLeonardo FrancalanciWed, 21 Sep 2011 14:35:34 -0000https://sourceforge.net835b8aea924e22e327a565a3e5f83633a41b3fdehttps://sourceforge.net/p/jsqlparser/feature-requests/5/Donating a pom.xml that you use to make the project buidlable with Maven. Would be great if we can get the \*.jar file to be uploaded to the central Maven repository also. See: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide I realize this will mean addtional work but it will help those of use who use Maven as the primary build tool. Best, hleofxquotes Sun, 27 Mar 2011 14:54:42 -0000https://sourceforge.netd5a5375864ecdf90cb783cc50cd13e3639ed4a15https://sourceforge.net/p/jsqlparser/feature-requests/4/Currently CAST expressions are not supported and makes the parser fail because CAST\(a1 AS DATE\) does not satisfy the grammar. Currently the Oracle outer join \(+\) is not supported and makes the parser fail. It would be great if queries like: select t1.a12 a, decode\(t2.a22, null, '0', '1'\) as b, cast\(t3.a31 as date\) c from t1, t2 join t3 where t1.a11\(+\) = t2.a21 could be parsed, even better if they could be interpreted to a certain extent.substrashFri, 04 Mar 2011 14:19:02 -0000https://sourceforge.netc24b1691af9131c658770600ff1c9a3f4cc31983https://sourceforge.net/p/jsqlparser/feature-requests/3/1\) DB2 supports "||" as a concatenation operator in a select expression; 2\) AS400 DB2 also can contain "QTEMP/" token in the columns names. Is it possible to add such a functionality? \(Please find an enclosed patch with those improvements\)Stanislav AmbartsumovThu, 03 Jun 2010 11:29:26 -0000https://sourceforge.netabfb19db7d7dd59e91519bbd8054999fd1efcf62https://sourceforge.net/p/jsqlparser/feature-requests/2/In most databases, a join query can also be written as a "where" condition referring to multiple "from" items. \(example: select t1.a, t2.b from t1, t2 where t1.id = t2.id\). This is currently not supported since only one FromItem can be inspected \(FromItem PlainSelect.getFromItem\(\)\). It would increase the usefulness if multiple "from" items would be allowed \(List PlainSelect.getFromItemList\(\)\). RaskolnikovSat, 07 Nov 2009 17:14:12 -0000https://sourceforge.nete896a580a0126dff594c97507cf1f2e72e2bfe7ehttps://sourceforge.net/p/jsqlparser/feature-requests/1/We use SQL to query the list of java objects rather than an ordinary database. The column names are mapped into the object fields. Currently JSqlParser allows only single dot, separating the table name from the column name. The java object can have much more nested objects. The simpliest solution would be to recognise the first dot as the table/column separator, but add all subsequent dots to the returned column name. This feature should be optional, having possibility to turn it on and off, for example, by the boolean getter and setter in CCJSqlParserManager. The possible workaround in to pre-process the query, replacing dot by, for example, '$'. The problem is that dots can also occur in fload values \(where a=5.0\) and string literals \(where chapter="1.2.2"\), where they should be preserved. So pre-processing is not promising to be simple.Audrius MeskauskasMon, 27 Dec 2004 08:37:57 -0000https://sourceforge.net761f15fa3c2449e91708e7b2fda4eeed77a9cc5f