Keep keyword before leading-dot float literal (issue #601)

[deepakganesh78]

Fixes #601.

Problem

Parsing a BETWEEN bound written as a float without a leading zero mis-tokenizes the statement:

sqlparse.parse("... where l_discount between .03 and .06")

BETWEEN gets demoted from a keyword to a Name, the WHERE body is grouped wrong, and .03 / .06 stop being standalone number tokens.

Cause

The lexer rule that supports schema . name member access:

(r'[A-ZÀ-Ü]\w*(?=\s*\.)', tokens.Name),  # 'Name'.

matches any word followed by whitespace + a period — including a keyword sitting in front of a float literal like .03. So between matched this rule and was tagged as a Name.

Fix

Add a (?!\d) negative lookahead so the rule ignores a period that begins a numeric literal:

(r'[A-ZÀ-Ü]\w*(?=\s*\.(?!\d))', tokens.Name),

schema.name / schema . name / a.b.c member access is unchanged; only the keyword-before-float case is corrected.

Tests

• test_between_leading_dot_float_issue601 — BETWEEN stays a keyword, AND stays a keyword, and .03 / .06 are Number.Float tokens (upper and lower case).
• test_keyword_before_qualified_name_still_grouped — guards that qualified-name grouping keeps working.

Full suite: 494 passed, 2 xfailed, 1 xpassed.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.16%. Comparing base (111b35c) to head (267f571).
⚠️ Report is 8 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #868      +/-   ##
==========================================
+ Coverage   97.13%   97.16%   +0.03%     
==========================================
  Files          31       31              
  Lines        3663     3704      +41     
  Branches      328      331       +3     
==========================================
+ Hits         3558     3599      +41     
  Misses         63       63              
  Partials       42       42              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.