From 0e67ccebcc838690b0ef33b4361d6aa113bed8f0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?javier=20ram=C3=ADrez?= Date: Thu, 8 Aug 2024 17:28:06 +0200 Subject: [PATCH] Update clients/date-to-timestamp-conversion.md Style fixes Co-authored-by: Nick Woolmer <29717167+nwoolmer@users.noreply.github.com> --- clients/date-to-timestamp-conversion.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/clients/date-to-timestamp-conversion.md b/clients/date-to-timestamp-conversion.md index 88bfee3b..505effe7 100644 --- a/clients/date-to-timestamp-conversion.md +++ b/clients/date-to-timestamp-conversion.md @@ -10,9 +10,9 @@ description: Python, Go, JAVA, JavaScript, C/C++, Rust, .Net, PHP, or Ruby. Most languages have a dedicated type for dates or timestamps, with the notable exception of C. In this guide, we show how to convert from a literal string representing a date into the native `Date` type, and then into a `Timestamp` type using Python, Go, Java, C, C++, Rust, C#/.NET, JavaScript/Node.js, Ruby, and PHP. -QuestDB has clients for Python, Go, Java, C, C++, Rust, Rust, C#/dotnet, and JavaScript/Nodejs. Some of the clients -can directly use the `Timestamp` type when using the client, while others need to convert the timestamp into an -integer representing the epoch time in microseconds. On each of the snippets, we add the extra conversion if needed. +QuestDB offers clients for Python, Go, Java, C, C++, Rust, C#/.NET, and JavaScript/Node.js. Some of the clients +can directly use a `Timestamp` type when using the client, while others need to convert the timestamp into a +long representing the epoch time in microseconds. We add such required conversions into the snippets. Please refer to the [ingestion overview](https://questdb.io/docs/ingestion-overview/) to learn more about the details of the client library for your language.