[
https://issues.apache.org/jira/browse/EMPIREDB-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808089#comment-17808089
]
Rainer Döbele commented on EMPIREDB-415:
----------------------------------------
Dear Jan,
I have looked at your example and I understand your point, but in theory the
fallback is OK, since you ask for a column named "ID" and you get a column
named "ID".
As mentioned above, if you change the code in line 621 to
{{ .selectQualified(EMP.ID, ...}}
then you will get the sql statement:
{{ SELECT t2.ID AS EMPLOYEE_ID, ...}}
and dle.hasField(DEP.ID) will return false as desired.
Changing something here would most certainly break existing code.
> DataListEntry.hasField / DataListHead.getColumnIndex
> ----------------------------------------------------
>
> Key: EMPIREDB-415
> URL: https://issues.apache.org/jira/browse/EMPIREDB-415
> Project: Empire-DB
> Issue Type: Bug
> Components: Core
> Affects Versions: empire-db-3.1.0
> Reporter: Jan Glaubitz
> Priority: Major
>
> I am using the DataListEntry and want to perform some action on it. So I
> created a method that get a DataListEntry as parameter and want to check if I
> it contains the correct column I need to use.
> I did this by using DataListEntry.hasField. This method uses
> DataListHead.getColumnIndex:
> {code:java}
> // Not found, try by name
> return getColumnIndex(column.getName());
> {code}
> turns out: it just checks for the name of the column. So if you check for
> TABLE_X.ID it just checks for "ID".
> I think this is a bug...?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
