starred/CoreStore-JohnEstropia
1
0
Fork 0
mirror of https://github.com/JohnEstropia/CoreStore.git synced 2026-07-21 12:08:39 +02:00
Code Issues 95 Packages Projects Releases 10 Wiki Activity

SectionBy Date - not string? #158

New Issue
Closed
opened 2025-12-29 18:23:51 +01:00 by adam · 5 comments
adam commented 2025-12-29 18:23:51 +01:00
Owner
Copy Link
Copy Source

Originally created by @akac on GitHub (Aug 15, 2017).

I am doing a sectionBy Date (they are stored as the beginning of day for that data type) - in the SectionBy clause, can I get the actual date instead of a string?

I should add - I've already changed my implementation to use a date interval instead as I thought about it a bit more and realized that using a Date like that would be problematic in different timezones - but for future if I wanted to use another value like an Int or something like a Bool - beyond having to parse a string and turn it into the value, is there a way to get SectionBy to be something other than a string?

Originally created by @akac on GitHub (Aug 15, 2017). I am doing a sectionBy Date (they are stored as the beginning of day for that data type) - in the SectionBy clause, can I get the actual date instead of a string? I should add - I've already changed my implementation to use a date interval instead as I thought about it a bit more and realized that using a Date like that would be problematic in different timezones - but for future if I wanted to use another value like an Int or something like a Bool - beyond having to parse a string and turn it into the value, is there a way to get SectionBy to be something other than a string?
adam added the question label 2025-12-29 18:23:51 +01:00
adam closed this issue 2025-12-29 18:23:51 +01:00
adam commented 2025-12-29 18:23:51 +01:00
Author
Owner
Copy Link
Copy Source

@JohnEstropia commented on GitHub (Aug 16, 2017):

The way CoreData interfaces sections is through Strings, I'm guessing because it's designed only to display section headers. One good way is to use DateFormatter to encode the section name, then use the same formatter to decode back to Date.

@JohnEstropia commented on GitHub (Aug 16, 2017): The way CoreData interfaces sections is through `String`s, I'm guessing because it's designed only to display section headers. One good way is to use `DateFormatter` to encode the section name, then use the same formatter to decode back to `Date`.
adam commented 2025-12-29 18:23:51 +01:00
Author
Owner
Copy Link
Copy Source

@akac commented on GitHub (Aug 17, 2017):

The problem with using date formatter for that is quite processor intensive. I did essentially above by using a day interval instead and parsing it from a string to a number. Works fine.

@akac commented on GitHub (Aug 17, 2017): The problem with using date formatter for that is quite processor intensive. I did essentially above by using a day interval instead and parsing it from a string to a number. Works fine.
adam commented 2025-12-29 18:23:52 +01:00
Author
Owner
Copy Link
Copy Source

@JohnEstropia commented on GitHub (Aug 17, 2017):

Thats a matter of caching the DateFormatter instance. But as long as it works for your use case it should be fine.
Just be careful that the sorting of intervals don't break your section ordering:
(numbers with fewer digits vs. longer ones)
e.g. "9" will be greater than "11" alphabetically

@JohnEstropia commented on GitHub (Aug 17, 2017): Thats a matter of caching the `DateFormatter` instance. But as long as it works for your use case it should be fine. Just be careful that the sorting of intervals don't break your section ordering: (numbers with fewer digits vs. longer ones) e.g. `"9"` will be greater than `"11"` alphabetically
adam commented 2025-12-29 18:23:52 +01:00
Author
Owner
Copy Link
Copy Source

@akac commented on GitHub (Aug 17, 2017):

I've been working with dates on iOS for 8 years - my performance tests are that DateFormatter parsing is still extremely slow, so I'd really like to not depend on that.

Good point on the intervals. Shouldn't be an issue realistically as we're talking about day intervals since 2000.

@akac commented on GitHub (Aug 17, 2017): I've been working with dates on iOS for 8 years - my performance tests are that DateFormatter parsing is still extremely slow, so I'd really like to not depend on that. Good point on the intervals. Shouldn't be an issue realistically as we're talking about day intervals since 2000.
adam commented 2025-12-29 18:23:52 +01:00
Author
Owner
Copy Link
Copy Source

@JohnEstropia commented on GitHub (Aug 23, 2017):

@akac I'll close this issue. Feel free to comment if there's anything else. Thanks!

@JohnEstropia commented on GitHub (Aug 23, 2017): @akac I'll close this issue. Feel free to comment if there's anything else. Thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
abandoned
corestore bug
discussion
duplicate
enhancement
fixed
fixed
help wanted
in progress
investigating
ios/compiler bug
irreproducible
looking for workarounds
not a bug
pending
pending docs update
pull-request
Mirrored from GitHub Pull Request
 question
regression
user bug
wontfix
No labels question
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/CoreStore-JohnEstropia#158