Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Do 15.08.2024 00:00:01 2.049.610 +1.147 100.539.771 49,1 Mastodon 4.3.0... 500 Mi 14.08.2024 00:00:05 2.048.463 0 100.426.123 49,0 Mastodon 4.3.0... 500 Mi 14.08.2024 00:00:05 2.048.463 +1.555 100.426.123 49,0 Mastodon 4.3.0... 500 Di 13.08.2024 00:00:00 2.046.908 +1.369 100.311.382 49,0 Mastodon 4.3.0... 500 Mo 12.08.2024 00:00:00 2.045.539 +1.270 100.192.858 49,0 Mastodon 4.3.0... 500 So 11.08.2024 00:00:10 2.044.269 +1.003 100.082.452 49,0 Mastodon 4.3.0... 500 Sa 10.08.2024 00:00:04 2.043.266 +1.405 99.975.166 48,9 Mastodon 4.3.0... 500 Fr 09.08.2024 00:00:03 2.041.861 +1.420 99.897.120 48,9 Mastodon 4.3.0... 500 Do 08.08.2024 00:00:05 2.040.441 +1.475 99.776.486 48,9 Mastodon 4.3.0... 500 Mi 07.08.2024 00:00:00 2.038.966 0 99.648.476 48,9 Mastodon 4.3.0... 500
Bob Peterson (@HootenHaller) · 12/2018 · Tröts: 816 · Folger: 30
Do 15.08.2024 16:51
Getting tripped up by @SwiftData again. Made a custom value type ComplexNumber which not only conforms to Codable but has a custom implementation using singleValueContainer.
My @model uses this for a property, but the resulting SQL schema has columns real and imaginary instead of phasor. Is there some simple technique or annotation to tell SwiftData to store using the Codable methods instead of deconstructing the value type to its component properties?
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0 · via Ivory for Mac