[ https://issues.apache.org/jira/browse/EMPIREDB-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807746#comment-17807746 ]
Jan Glaubitz edited comment on EMPIREDB-415 at 1/17/24 2:51 PM: ---------------------------------------------------------------- Hi Rainer, yes, the TRUE case works. The fallback is my problem. If you provide a e. G. ID column of Table1 but there is only ID Column of Table2 it returns TRUE - but its not really the case. Maybe the fallback should be skipped if column is an instance of DBTableColumn? was (Author: derjan): Hi Rainer, yes, the TRUE case works. The fallback is my problem. If you provide a e. G. ID column of Table1 but there is only ID Column of Table2 it returns TRUE - but its not really the case. > 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)