Ahem. What my esteemed colleague
meant to say is that EA supports a large number of underlying databases, so in order to help with a SQL query it's good to know what database you're running EA on since the SQL dialects differ.
(If you're in an .EAP file it's an Access database, Access 3.5 or 4.0 depending on your settings; a .feap file is Firebird.)
But on this occasion it's easier than that. The
t_attribute.ea_guid column does not contain any semicolons at all. That's an artifact from (most likely) you copying the data from the search results window, in which case EA adds semicolons as column separators. An ea_guid column is present in many tables, and it always contains only the GUID itself and the curly brackets surrounding it.
(All you religious nutters out there, PLEASE let's not get into a discussion on whether the brackets are part of the GUID or not.)
(Nor one on whether it's "brackets" or "braces.")
(Nor indeed one on whether I placed the full stop correctly there.)
I think the problem is that you're in an .EAP file, which is to say an Access database, but you're using what looks like Transact-SQL, which is appropriate for SQL Server but not for Access. More simply, you're using the wrong wildcard character. Try
select t_connector.Connector_ID
from (t_connector inner join t_attribute on t_connector.Start_Object_ID = t_attribute.Object_ID)
where t_attribute.Stereotype = 'Stamtabel'
and t_connector.StyleEx like '*' + t_attribute.ea_guid + '*'
Note also that it matters whether you are creating
a search definition, or using the SQL scratch pad. If you are creating a search definition, you can use the #WC# macro to resolve the situation and make your query more robust, but the scratch pad sends your queries straight through to the database engine so there you need to use the correct syntax for that engine.
HTH,
/Uffe
