Book a Demo

Author Topic: Documentation is not updated for SQLite database  (Read 5744 times)

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Documentation is not updated for SQLite database
« on: June 16, 2022, 05:25:44 pm »
In the documentation the fact that SQLite is now also an option as database is not reflected.
There are a few places where this is missing. One of them is: https://sparxsystems.com/enterprise_architect_user_guide/16.0/the_application_desktop/creating_filters.html

Reported

Geert

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Documentation is not updated for SQLite database
« Reply #1 on: June 17, 2022, 01:00:25 am »
Does anyone know what I should put for SQLite as dbName between the #DB=<dbName>#?
I tried SL3 and SQLite, but neither seems to work.

Geert

wivel

  • EA User
  • **
  • Posts: 243
  • Karma: +12/-1
  • Driven by Models
    • View Profile
Re: Documentation is not updated for SQLite database
« Reply #2 on: June 17, 2022, 05:51:06 am »
Or it could be that Sparx have forgotten to add it to the list of databases.

Henrik

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Documentation is not updated for SQLite database
« Reply #3 on: June 17, 2022, 06:04:51 am »
I was about to say that an hour ago xD

q.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Documentation is not updated for SQLite database
« Reply #4 on: July 05, 2022, 04:42:16 pm »
For those interested, the DB name for SQLite is SL3

So if you want to make a query with a specific part for SQLite you'll need to use #DB=SL3#

This is what it looks like in an SQL fragment. this fragment works for both SQL Server as SQLite.
For SQL Server I need [Description-Formatted] whereas the SQLite syntax requires `Description-Formatted`

Code: [Select]
select a.Name as AttributeName, a.Type as Format, a.LowerBound, a.UpperBound
, tvacc.VALUE as Accuracy, tvcri.VALUE as Critical, tvdtk.VALUE as DataKind, tvgdpr.VALUE as GDPR, tvinte.VALUE as Intern_Extern, tvqp.VALUE as QualityPeriodicity
, tvra.VALUE as RisAppetite, tvrc.VALUE as RiskClassification, tvsui.VALUE as Suitability
, tvts.VALUE as Timesliced
, a.Notes as #DB=SL3#`#DB=SL3##DB=SQLSVR#[#DB=SQLSVR#Description-Formatted#DB=SL3#`#DB=SL3##DB=SQLSVR#]#DB=SQLSVR#
 from t_attribute a
left join t_attributetag tvacc on tvacc.ElementID = a.ID
and tvacc.Property = 'Accuracy'
left join t_attributetag tvcri on tvcri.ElementID = a.ID
and tvcri.Property = 'Critical'
left join t_attributetag tvdtk on tvdtk.ElementID = a.ID
and tvdtk.Property = 'DataKind'
left join t_attributetag tvgdpr on tvgdpr.ElementID = a.ID
and tvgdpr.Property = 'GDPR'
left join t_attributetag tvinte on tvinte.ElementID = a.ID
and tvinte.Property = 'Intern_Extern'
left join t_attributetag tvqp on tvqp.ElementID = a.ID
and tvqp.Property = 'Quality Periodicity'
left join t_attributetag tvra on tvra.ElementID = a.ID
and tvra.Property = 'Risk Appetite'
left join t_attributetag tvrc on tvrc.ElementID = a.ID
and tvrc.Property = 'Risk Classification'
left join t_attributetag tvsui on tvsui.ElementID = a.ID
and tvsui.Property = 'Suitability'
left join t_attributetag tvts on tvts.ElementID = a.ID
and tvts.Property = 'Timesliced'
where a.Object_ID = #OBJECTID#
order by a.Pos, a.Name

Geert