Which is what you said it should be in the comments.
I suggest you ask a question on Stack Overflow with clearer requirements - it'll be easier to reply there than to switch between Gitter and dotnetfiddle
@Doggie52 - I'm suspicious of the intent in that code, though. It's implying that you're deriving the date to be closed off of the "current" date of some specific location. If close is run too late (or early, for locations east of London), that's going to change the date that gets reported (so you might close the same day twice). Business dates are only kinda related to actual calendar dates - I would normally prefer to use an explicitly chosen date for open/close (you can derive the date for user confirmation, though).
It also makes me suspicious of the use of 10:00AM. Either you have an arbitrary "business date" that you explicitly open/close and bucket sales into, and thus "bucket start/end time" is irrelevant, or you're bucketing based on the absolute
Instant(even if the buckets are based off of home office local time), and the time in any individual location is irrelevant.
Hey @Clockwork-Muse - FYI this is part of a trading algorithm where a decision needs to be made at a specific time of day, every day. This decision time of day is 10AM Ldn time and is explicit. My input is a current datetime from the system that I know the timezone of. The reason I'm using the date part of the input to get the decision time is to avoid DST ambiguities.
I understand the MWE prompts a lot of questions but I did my best to remove things that didn't factor in.
I've done some further digging and I believe the error lies elsewhere and in how I assumed my input to be a 0-tick "whole" hour whereas in reality it was often a few ticks after the hour.
I understand the MWE prompts a lot of questions but I did my best to remove things that didn't factor in.
I've done some further digging and I believe the error lies elsewhere and in how I assumed my input to be a 0-tick "whole" hour whereas in reality it was often a few ticks after the hour.
Hi, I'm working with genealogical data and I need to be able to store a dynamic date portion, that can either be a full
1) Is there a generalized entity that can hold this piece of data?
2) Is there a way to store such a column with EF Core and sort rows by it?
Thank you!
DateTime, Date, AnnualDate etc, all stored with EF Core.1) Is there a generalized entity that can hold this piece of data?
2) Is there a way to store such a column with EF Core and sort rows by it?
Thank you!
1) No. In a functional language you'd want what's known as a discriminated union, so you probably want to mimic that. Keep in mind that the moment somebody is born is technically an
2) Not by default. For one thing, what meaningful sorting are you planning on doing between
Instant, although for historical/legal reasons it's stated as some sort of ZonedDateTime (with resolution in minutes).2) Not by default. For one thing, what meaningful sorting are you planning on doing between
LocalDateTime values and AnnualDate values? LocalDateTime naturally sorts by year first. From the database side, your best bet is likely a set of nullable columns (setting less precise ones if a more precise one is specified), plus a set of separated, derived columns to perform searching/sorting on.
Hey and thanks for your detailed reply!
Let me narrow it down and say I want to have month/day + optional year, then be able to search whos birth-day or memorial-day happens today, so year is irrelevant to my query, but I need to be able to store and retrieve it. Are two separate columns the only solution?
Let me narrow it down and say I want to have month/day + optional year, then be able to search whos birth-day or memorial-day happens today, so year is irrelevant to my query, but I need to be able to store and retrieve it. Are two separate columns the only solution?
If you have an "optional" piece of data, in SQL-land that's a nullable column. You can abstract it by creating a custom type (which is a feature underutilized in most deployed applications) that does things like auto-convert from a date-time. Doing separate columns would also help with querying independently from year (that is, have another index on that particular column/pair).
Or, if you can guarantee that you always have a full date (birthdays always fall into this category, and for memorial dates you could use the first occurrence), you can construct all possible "first" dates with the use of a number/calendar table.
Hi! Anyone here who by any chance remember that original video from a talk that the creator of Nodatime gave, about how the BCL datetime construct is essentially broken and introducing Nodatime? I wanna show it to a coworker, and I want to be sure I find the same video I once saw because it was very good.
In terms of critiquing the BCL construction, this blog post is probably the best option: https://blog.nodatime.org/2011/08/what-wrong-with-datetime-anyway.html
If you mean the "Humanity: Epic Fail" talk, I don't think the video of that exists any more, but I have a blog post about it: https://codeblog.jonskeet.uk/2009/11/02/omg-ponies-aka-humanity-epic-fail/ (With currently broken pictures - I need to fix that...)
@HEskandari: Depending on the reason for contact, either email me directly (skeet@pobox.com), email the Google group, or file an issue in GitHub.
(I assume TimeZoneInfo.Local.Id returns "Local" or something similarly useless? I think we use the ID or name if possible.)
(It might be worth asking about this on GitHub - I actually get notified of changes on GitHub much quicker than on Gitter... and it leaves a more lasting record.)
(Hadn't actually checked.)
@artur-malendowicz-gain: Could you check what DateTime.Now returns on the device? Definitely worth filing a GitHub issue with a lot more information.
the latest NZD file I got is published on 2019 but it can only reach 2025.
I am wondering if we can get a file that can reach 2050
Hi all. I really like NodaTime and would like to use it. But I need some help to find answers to a few questions. It would be awesome if you can help with it. Is it possible to use NodaTime with AspNetCore? I'm trying to recieve query param of type Instant but with no success. It looks like there are no ModelBinder and I can't find it. Environment is: Windows 10, AspNetCore 2.2 and NodaTime 2.4.6. JSON parsing works. But unfortunatelly with query/path/form params does not. Thank you in advance
Thank you for quick reply. It might be quick fix. But if does not - sure, I will create question on SO. If you never mind I'll try to explain what problem I got. JSON serialization and deserialization works fine. I can't receive plain arguments (Instant in this case). Exception message told me that there are no ModelBinder. Should I register comething special for it? Thank you again.
Hi all. I'm using nodatime beta1 in my project and I got problem with parsing ZonedDateTime. It looks like there are no TypeConverter for it. Instant, OffsetDateTime, LocalDate works great. But for ZonedDateTime I got error: Could not create an instance of type 'NodaTime.ZonedDateTime'. Model bound complex types must not be abstract or value types and must have a parameterless constructor. Is it by design and I should create ModelBinder for it or this is a bug? Thanks in advance
I've filed nodatime/nodatime#1407 to track that
Hey does anyone know if NodaTime Instant serialises/deserialises correctly when using Json.net and ASP.NET Core 3.0 Preview 9? I'm not able to get things to work at all when using the ConfigureForNodatime extension
services.AddMvc().AddNewtonsoftJson((options) => options.SerializerSettings.ConfigureForNodaTime(DateTimeZoneProviders.Tzdb));
and if I just ignore adding the extension I just get 1 January 1970 as the Instant values - looking at Fiddler, the serialisation for the field is empty. Interestingly, Duration does serialise correctly in the same object over the same Http Get.
I'm calling the controller from a Blazor client side app if that makes a differenc too?
@ekwus: This would be best asked on Stack Overflow. You might want to look at the question slightly earlier in the chat though: https://stackoverflow.com/questions/57753258
@jonskeet_twitter Thanks I'll post it on SO. I did see the question above however it answers it for ASP.NE Core 2.2 and the AddJsonOptions extension is gone from 3.0. I've tried a few ways around using it with the AddNewtonsoftJson extension but nothing works. Anyway, I'll put it all on SO to ensure it gets captured for others too. Cheers
@jonskeet_twitter Further update. I create a clean ASP.NET Core 3.0 project to push to Github as a reference for the StackOverflow question but the serialisation was working correctly after I figured out the new extensions. Looks like its a setup issue in my other project. I'm also pulling the values from LiteDB in that app so possibly an area for me to look at too. Cheers
Hello to all. I'm migrating my project to EF Core 3. As I see currently I can use instance of Instant (local variable for example) or SystemClock.Instance.GetCurrentInstant() in my queries. Is it possible to use an injected IClock or this is by deisgn to not allow it? Thank you in advance
@Alantoo: Are you using a particular EF Core plug-in library? It could be converting SystemClock.Instance.GetCurrentInstant() into SQL to fetch the current time on the server. I'm afraid I don't really understand enough about what your context to help you - I'd strongly suggest asking a new question on Stack Overflow with more detail.
@jonskeet_twitter Yes, I'm using it. It works great with SystemClock.Instance.GetCurrentInstant(). It would be awesome to have ability to use instance of IClock in queries as well. It can help a bit in unit tests. I just would like to know if there any plans to implement it or maybe it not works only with EF Core 3 and it will be fixed later? Thank you for your answers
Again, I don't have enough context here. Without even knowing which package you're using, I can't possibly know whether there's a plan to implement the use of arbitrary clocks - but I wouldn't expect so, given that you can't generate SQL for "what's the time that some arbitrary IClock implementation would return". Please bear in mind that the NodaTime package itself doesn't know anything about EF Core, so I'm pretty sure you're using some other package - I strongly recommend finding the GitHub repo for that project, and asking a question there.