Replace %20 characters in URL with a dash (-) | Code is from MySQL

@123468743867143 you do not want to "decode %20 into dashes" in the browser. Instead, generate a dash-separated slug on the server, then place that slug in the URL. Note that urldecode('%20') returns a space, not a dash; browsers also do not rewrite - to %20 because hyphen is an unreserved URI character. Spaces are the ones that must be encoded as %20 (or + in form-style queries). (rfc-editor.org)

A simple, safe PHP pattern is to normalize the title, then build the link. This expands on @Manuz’s suggestion with a stricter slug and proper escaping:

$title = $record['title'];                       // e.g. "970 South Bald Head Wynd"
$slug  = preg_replace('/[^A-Za-z0-9]+/', '-', $title);
$slug  = trim($slug, '-');                       // "970-South-Bald-Head-Wynd"

$url = 'details.php?listid='.(int)$record['listingid'].
       '&title='.rawurlencode($slug);            // hyphens stay as-is
echo '<a href="'.htmlspecialchars($url, ENT_QUOTES).'">'.$title.'</a>';

If you want cleaner paths, pair that slug with a rewrite so the URL reads /details/800/970-South-Bald-Head-Wynd while still hitting details.php under the hood:

# .htaccess
RewriteEngine On
RewriteRule ^details/([0-9]+)/([A-Za-z0-9-]+)/?$ details.php?listid=$1&title=$2 [L,QSA]

On the SEO point @~s.o.s~ raised: keeping readable words helps both users and Google. Google explicitly recommends using hyphens to separate words in URLs, as it makes concepts easier to identify; underscores are not recommended. Your example 970-South-Bald-Head-Wynd is exactly the style they show. (developers.google.com)

Practical tips:

• Keep listid as the source of truth; if the incoming slug does not match your current slug, 301-redirect to the canonical one to avoid duplicates.
• When outputting links in HTML, always escape & to & (the htmlspecialchars in the snippet handles this). For background on when characters must be percent-encoded in URLs, see MDN’s percent-encoding overview. (developer.mozilla.org)