Defect #1701
closed
Entity Event: add localization for bad uuid value used in filter.
Added by Radek Tomiška over 5 years ago.
Updated over 5 years ago.
Description
Add localization for bad uuid value used in filter on entity id, root and parent event id.
Add search by event id int simple "fulltext" search.
- Status changed from New to In Progress
- Status changed from In Progress to Needs feedback
- Assignee changed from Radek Tomiška to Ondřej Kopr
- % Done changed from 0 to 90
- Status changed from Needs feedback to Resolved
- Assignee changed from Ondřej Kopr to Radek Tomiška
- % Done changed from 90 to 100
MSSQL queries
With id:
select
count(idmentitye0_.id) as col_0_0_
from
idm_entity_event idmentitye0_
where
lower(idmentitye0_.owner_type) like '%579427fe-e537-4578-a54c-040d4c0056e3%'
or lower(cast(idmentitye0_.owner_id as varchar(255))) like '%579427fe-e537-4578-a54c-040d4c0056e3%'
or lower(cast(idmentitye0_.id as varchar(255))) like '%579427fe-e537-4578-a54c-040d4c0056e3%';
With owner type:
select
count(idmentitye0_.id) as col_0_0_
from
idm_entity_event idmentitye0_
where
lower(idmentitye0_.owner_type) like '%idm.core.model.entity%'
or lower(cast(idmentitye0_.owner_id as varchar(255))) like '%idm.core.model.entity%'
or lower(cast(idmentitye0_.id as varchar(255))) like '%idm.core.model.entity%';
For owner type works query well, but for id doesn't. MSSQL database transform ID's into some strange strings. For now is know issues for this database: https://wiki.czechidm.com/devel/documentation/compatibility#microsoft_sql_server
- Status changed from Resolved to Closed
Also available in: Atom
PDF