fix(sqllab): pass DB id instead of name

[betodealmeida]

SUMMARY

#31590 broke SQL Lab by replacing the dbID with a name:

https://github.com/apache/superset/pull/31590/files#diff-ea7a7f3b0884ed0d868929c970403455028773ec29a90c6ef8b507d6b4e9ab34R199

This PR fixes it.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

• Has associated issue: Fixes SQL Lab Fails to Save Tab State — Incorrect database_id sent as string instead of integer #33935
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[korbit-ai]

Based on your review schedule, I'll hold off on reviewing this PR until it's marked as ready for review. If you'd like me to take a look now, comment /korbit-review.

Your admin can change your review schedule in the Korbit Console

[korbit-ai]

I've completed my review and didn't find any issues.

Files scanned

​

File Path	Reviewed
superset-frontend/src/components/DatabaseSelector/index.tsx	✅

Explore our documentation to understand the languages and file types we support and the files we ignore.

Check out our docs on how you can make Korbit work best for you and your team.

Loving Korbit!? Share us on LinkedIn Reddit and X

[mistercrunch]

LGTM, trying to understand what happened here and whether we should expect more funk from the large merge. I'm the one on the git blame on master because of the "squash and merge" strategy, but I pulled the git blame from template_less and see this:

b8354785147 (Mehmet Salih Yavuz    2025-04-08 15:14:15 +0300 356)

Tagging Memo to see if he has a take on how this slip in. Guessing intricate merge conflict...

[rusackas]

Updated the description to auto-close #33935, FYI.

[betodealmeida]

LGTM, trying to understand what happened here and whether we should expect more funk from the large merge. I'm the one on the git blame on master because of the "squash and merge" strategy, but I pulled the git blame from template_less and see this:

b8354785147 (Mehmet Salih Yavuz    2025-04-08 15:14:15 +0300 356)

Tagging Memo to see if he has a take on how this slip in. Guessing intricate merge conflict...

Ah, it's because it generates <div id="1"/>, but an ID can't be a number. We need a better way of passing the DB ID.

[betodealmeida]

Seems to be working now in master.

[hai-ld]

@betodealmeida could you please re-open this PR? master doesn't work for me (as of 308007f). It only works after I apply your changes.

[michael-s-molina]

I can confirm the bug is still happening on master.

[HarshithGamini]

Is this fix getting merged? I do face this issue as of latest master.

[betodealmeida]

I need to fix the failing test. Will do it ASAP.

[rusackas]

According to @dosu, this may fix #34130 as well.

[betodealmeida]

OK, let's merge this as soon as it's green!

[mistercrunch]

Thanks for fixing this! 👏