adsnaider
adsnaider
I should mention, I would be happy to contribute this feature if I can get some direction to get started.
@the-mikedavis, that's a fair point. I can see myself adopting a different workflow given that it's a different editor. However, I do think that there's good reasons to have tabs...
I went ahead and implemented the Allocator trait in #8106
I was actually seeing the `Error: An ARM specific error occurred.` with [email protected]
Fascinating, I'm fairly confident I was seeing this error on 0.21.1 when I installed using cargo. However, using the prebuilt binary I see no such issue.
Made some updates. Still need to: - [ ] Partition the table by date - [x] Split the table to store the last_used data in a different table
@jsha I got a couple of questions for you :) 1. I agree partitioning would be useful. Do you think it would be best to have a creation_date column and...
> I hadn't noticed that there's no creation_date column We don't have `creation_date`, but we have `created_at` (which is a timestamp) I agree with starting with the basics for now....
@jsha I'm having trouble figuring out how partitioning will fit alongside the rest of the infrastructure. I can define the table to be partitioned by primary key but the partitions...
@bjorn3 or @pietroalbini do either of you know who I should contact in order to setup automatic creation/deletion of the partitions as a cron job within the server?