potiuk commented on PR #24320: URL: https://github.com/apache/airflow/pull/24320#issuecomment-1156443425
@potiuk yes of course in sqlalchemy doc https://docs.sqlalchemy.org/en/14/core/engines.html#database-urls has link to [RFC-1738](https://www.ietf.org/rfc/rfc1738.txt) spec. This spec in point 3.3 has this string If neither <path> nor <searchpart> is present, the "/" may also be omitted.. For me this string means that we should omitt / only in case when we don't have both of parameters <path> and <searchpart> if we have one of them the / should be. Correct me please if I make mistake? Ah OK. Thanks for pointing it out. Indeed '/' was obligatory in 1738. SQL alchemy follow the older URL RFC (1738) which has actually been deprecated by URI (3986) - even though URI would be more approprite :D : > This document obsoletes [[RFC2396](https://datatracker.ietf.org/doc/html/rfc2396)], which merged "Uniform Resource Locators" [[RFC1738](https://datatracker.ietf.org/doc/html/rfc1738)] and "Relative Uniform Resource Locators" [[RFC1808](https://datatracker.ietf.org/doc/html/rfc1808)] in order to define a single, generic syntax for all URIs. It obsoletes [[RFC2732](https://datatracker.ietf.org/doc/html/rfc2732)], which introduced syntax for an IPv6 address. It excludes portions of [RFC 1738](https://datatracker.ietf.org/doc/html/rfc1738) that defined the specific syntax of individual URI schemes; those portions will be updated as separate documents. The process for registration of new URI schemes is defined separately by [[BCP35](https://datatracker.ietf.org/doc/html/rfc3986#ref-BCP35)]. Advice for designers of new URI schemes can be found in [[RFC2718](https://datatracker.ietf.org/doc/html/rfc2718)]. All significant changes from [RFC](https://datatracker.ietf.org/doc/html/rfc2396) [2396](https://datatracker.ietf.org/doc/html/rfc2396) are noted in [Appendix D](https://datatracker.ietf.org/doc/html/rfc3986#appendix-D). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
