Niwaka
Niwaka
> Another choice is as @fengjiachun said, let's not change the region's TTL but just the database options. I prefer the second solution. It's much simpler, and altering many tables...
I'll implement this feature with the following high level steps: - [ ] Implement `DatabaseMetadataManager`. - [ ] Implement `AlterDatabaseProcedure`. - [ ] Allow parser to handle sql like `alter...
Sorry for the delay in implementing this. I'll submit a first PR next week.
@killme2008 I'm interested in this. I'd like to use it. If GreptimeTeam accepts this feature, I'd like to work on it. Maybe the first PR is to add support for...
@waynexia Thank you for sharing! Your implementation looks like it's very helpful!! I'm sorry for pointing a very minor issue, but as far as I understand, it seems like `chrono`...
@killme2008 By the way, I think we could support Questdb's modifier syntax like: ```sql select * from monitors where ts within '2018-01;-3d'; ``` Do you think it's worthwhile to support...
Related to #8.
@annethereshewent Could you share a minimal example to be able to reproduce the error?
@waynexia @evenyag Are you working on this issue? If not, I'm interested in this issue. > PostgreSQL returns an error if it can't convert the string literal to an integer....
Hi @alamb, Is this feature already supported? `ALL` seems not to work right now: ``` SELECT 1 = ALL(ARRAY[1,1,1,1]); This feature is not implemented: Unsupported ast node in sqltorel: AllOp...