Age | Commit message (Collapse) | Author |
|
They are practically always useless, often misleading or obsolete.
Change-Id: I2d32182a31349c9fb3b982498fd22d93e84c0c0c
|
|
Change-Id: I6c6b9452014940e09f8f4b7466c5a5f562c9fff5
|
|
Change-Id: Ic573e5ae63fdfb3d4ff79eb6d81fe0f4b058d582
|
|
Change-Id: Icc55a6b485341e3be0d3e96f51f41a2bba1629c1
|
|
Change-Id: Id30805f09bc359c6f66d87f050427c0e586ec93d
|
|
not only one.
Change-Id: I1f611dda6a98fb6244409c0cd1fc87fc9dfaa8c3
|
|
Change-Id: I709305d4ec3c37d3fc1c2c911551174f8cfbb883
|
|
Change-Id: Ia20eec6e868579ed31e478514b7f2722a0972094
Reviewed-on: https://gerrit.libreoffice.org/5828
Reviewed-by: Thomas Arnhold <thomas@arnhold.org>
Tested-by: Thomas Arnhold <thomas@arnhold.org>
|
|
Compiler plugin to replace with matching number(), boolean() or OUString ctor,
ran it, few manual tweaks, mark as really deprecated.
Change-Id: I4a79bdbcf4c460d21e73b635d2bd3725c22876b2
|
|
Change-Id: I06057fd5fddde278333bf3b65388c70d30b69d79
|
|
Change-Id: I5fe746ed08a7b1124465231b6e85475da5490904
|
|
Change-Id: I38354405acbbdb27b9e7ce1d19e862b7b352c850
|
|
Change-Id: I7d82e34545a5aab657f3156b8c5b23c8a8531a11
|
|
as opposed to *table* columns,
and notwithstanding HSQLDB 1.8 (our embedded database) bugs.
Actually, supporting ORDER BY on non-select (but table) columns is OPTIONAL for DBMSs
(but quite common)
Change-Id: I6725dfda36b09429a78262bff6f3d3e3dd9032b6
|
|
Change-Id: I5a5df020dd6900e28a9db94bfa179baa3f59dc4a
|
|
as opposed to no match
Change-Id: I811abd9df5b6cc617c28ab330cecb406cd11e709
|
|
A couple of headers now need to be public because they are indirectly
included in other modules.
Change-Id: Id01945197b67183a0a042e854289875ae147a0eb
|
|
Change-Id: I29a3a68f9ee434332cad7199a90a1b01c22fbe0e
|
|
Change-Id: Ie54546ef97fe102de09888ce9c7eefe6c879aae4
|
|
Change-Id: Id80d373d93df140b8fc0d0d0c44044b94ceb97a9
|
|
ensures nobody mistakenly modifies it, and makes other code get
a non-empty string where empty string is expected.
Change-Id: I477edd0e589444da19b68381234eb5e85ecd54cc
|
|
Undo problematic pollution by sqlbison.hxx
Since with post-2008 (2.4 and later) bison that "#define SQLyylex"\is not active in sqlflex.l, this forces the situation o be the same in all versions of bison, and should notreak anything by itself.
Change-Id: Ie65e3f6cc61dc97adc1d530e3781306ecd176b17
|
|
Change-Id: Ia54673f3e689a49b3e9101ae4cf5b57f1e68f592
|
|
Change-Id: I1b310119c08052949e975bfa3838e229d4e140b2
|
|
the TABLENAME property contains the *original* tablename, but this column should have the query table alias as table name
Change-Id: Ieeb362f38b701b92998e293dda474bad36e5e577
|
|
This fixes parsing failures, like e.g.
warn:legacy.osl:30429:1:dbaccess/source/core/api/SingleSelectQueryComposer.cxx:783: OSingleSelectQueryComposer::getColumns: could not parse the column retrieval statement!
when opening query "Balance" of https://bugs.freedesktop.org/attachment.cgi?id=71964
OTOH, since we have reduce/reduce conflicts, we might have true
ambiguities in our grammar. This change makes the parsing fail
in the presence of full-expression ambiguities instead of making
a ~arbitrary choice.
Change-Id: I88574da91045dd52f198f193c78d144302f298a4
|
|
don't remove parentheses around subqueries
(without the parentheses, it is not valid SQL)
Change-Id: I4e9c55cea0276f10b0f97e31bc329949aba5b989
|
|
Change-Id: I509984a6029b6a86fd1ee3f947394af9cdf71c6a
|
|
Change-Id: I3597aadab8b13703ed7b7731d530320c4e5999be
|
|
When converting a parse tree to SQL snippet for a predicate in the
context of a column, we skip the name of the same column in 'simple'
cases.
This is used mainly in the "Criterion" lines of query design,
and in the search/filter dialogs of forms, tables, etc.
In all other cases (such as when creating a full SQL command, or for
references to *other* columns than the context one), the column name
must be printed out.
In this respect, the condition "should we skip the column name?" in
impl_parseLikeNodeToString_throw was buggy, and different from the
one in the general case (in impl_parseNodeToString_throw), leading
to generating invalid SQL like:
SELECT foo, bar FROM baz LEFT JOIN qux ON LIKE qux.quu
instead of
SELECT foo, bar FROM baz LEFT JOIN qux ON baz.baa LIKE qux.quu
Change-Id: Ie14fce319554a66feb0fd0ce1a03d947a46a820a
|
|
This reverts commit 10777b37536be16c6d2e167b59e9e31e37ba3517.
The problem has been fixed in a more safe way by making columnMatchP
treat the case where rParam.xField is not set instead of requiring
it from all callers.
Change-Id: Ic68a764e08446a7b669c6030c2bcd55c7d31772b
|
|
Change-Id: Id994ab5aed6172d8a93fd331a366fca10a663a48
|
|
- replaced RTL_CONTEXT_ with SAL_INFO
- replace OSL_* with SAL_*
Change-Id: If89af70767c3fdc4b1d0cb5e51033ca98583bc5d
Reviewed-on: https://gerrit.libreoffice.org/4286
Reviewed-by: Noel Power <noel.power@suse.com>
Tested-by: Noel Power <noel.power@suse.com>
|
|
Problem caused by commit:
16c9ce4877def18ca4578171a96615a632d08092
This commit contains code deduplication.
The deduplication removed one needed check (rParam.xFiled.is()),
which causes segfault when member function of rParam.xField
is called inside columnMatchP().
Change-Id: Ibbdaa758dbbce4b76094e6cc120022ef276b30c4
|
|
lets try this hack, if it fails revert and I'll just
manually update the baseline with a newer flex than
flex-2.5.4a-41.fc6
Change-Id: If644489e80fc4e4cdba97808af0fe4d544d08646
|
|
|
|
Change-Id: Ic05de69951b28b9cc8d62f0a534b507c424e6b25
|
|
Change-Id: Ib3957fbadf6bfebfaabd5bef09aaf7ab21862cd6
|
|
Basically, in first children of infix predicates in search_conditions
Change-Id: I0e2f8fbdde023b088f33d2e2fcbd41110f0e02a8
|
|
Change-Id: I94c274e8afc70fa702063d61139299a7bde9165b
|
|
As opposed to only the column name
Change-Id: I261d13f23214f950daa55a5b63cd486e59a0e127
|
|
Change-Id: Ie794e91783f8eaacf236070e7cdeb5b5f4361e9b
|
|
Change-Id: I157e0e84cbc9832dd863607b8f52359596b51c8c
|
|
Change-Id: I13aaf37421c7652e8e293759e9f563fc76cb1344
|
|
Change-Id: I610ecd58f3f7fa7f3ab04db8b17259bbc54c2b74
|
|
|
|
Change-Id: Ica2d3485c62f44311f612ade20924690bfbb2666
|
|
nCount == 5 is impossible; the grammar has changed since this code was written.
It used to refer to case '(' joined_table ')' range_variable op_column_commalist
which has become just '(' joined_table ')'
which thus has (by definition) no table range (alias).
Case changed in mega-(merge-)commit:
commit c41efc6d0b2740be4243fd696385f8dbcec0aefe
Author: Jens-Heiner Rechtien <hr@openoffice.org>
Date: Wed Nov 19 17:43:08 2008 +0000
CWS-TOOLING: integrate CWS dba301a_DEV300
which seems to have done the other necessary adaptations to this code
and elsewhere.
Change-Id: I96ddbefbf34d6c155435b78aa9e5037a760232ed
|
|
Change-Id: Icf3b500b9317cd45b3dc424da155ab6c48227ea5
|
|
Modules sal, salhelper, cppu, cppuhelper, codemaker (selectively) and odk
have kept them, in order not to break external API (the automatic using declaration
is LO-internal).
Change-Id: I588fc9e0c45b914f824f91c0376980621d730f09
|