-
> A Timestamp MUST be formatted according to ISO 8601.
> A Timestamp SHOULD* be expressed using the format described in RFC 3339, which is a profile of ISO 8601.
ISO 8601 forbids an offset of `-00…
-
Hi,
I'm experiencing errors parsing lucene strings that refer to a date-time value with timezone that is not wrapped with double-quotes. See for example:
```
>>> from luqum.parser import parser
…
-
Schema.org datatypes are not good:
- they go against standard XSD datatypes that are the foundation of both XML and RDF.
- they are tentative (don't specify a lexical representation), eg schema:Numb…
-
### Is your feature request related to a problem? Please describe.
The python client ("python-nextgen" as of v6.6.0, "python" in v7+) allows specifying the `datetimeFormat`, but python datetime sta…
-
Currently Cellfie will do nothing regarding the data as UNIX timestamp and it will just treat it as an ordinary string. The transformation will not produce the right date/time literal representation.
…
-
```sql
create table test (
tz timestamptz
);
insert into test values ('0001-01-01 00:00:00Z');
```
will cause ` Parse error: Can't cast string to timestamp (expected format is YYYY-MM-DD HH…
-
### PROBLEM
## The language description document does not specify the acceptable time string formats for the "delay", "duration", "frequency", and "time" modifiers.
### POTENTIAL SOLUTION
ISO 8601 is…
-
ISO 8601 supports nanosecond level formats. For compatibility with implementations which utilize nanoseconds, its difficult to work around this incompatibility.
I realize the documentation mentions…
-
![image](https://github.com/avaidyam/ProjectEHR/assets/1361003/f7597009-58c5-4ddc-98f5-cdb2f3e2ea8c)
-
## Enhancement Task