如何正确验证价格并在数据库中存储？含前端代码示例

Great question—handling price input and storage correctly is crucial to avoid formatting glitches and precision headaches. Let’s break this down step by step, covering frontend improvements, backend validation, and proper database setup:

1. Polish Frontend Handling #

Your existing jQuery blur handler is a good start for formatting, but we need to make sure:

• The displayed value is user-friendly (like 2,00€)
• The value sent to the backend is a clean numeric format (like 2.00) to avoid parsing errors

Here’s the refined frontend code:

Updated jQuery for Formatting & Submission Prep #

// Format price to 2 decimal places with comma separator on blur
document.getElementById("price").onblur = function() {
  // Strip out non-numeric characters except commas, dots, and minus (for edge cases)
  let cleanRawValue = this.value.replace(/[^\d,.-]/g, '');
  // Convert comma-separated decimals to dot for numeric parsing
  let numericValue = parseFloat(cleanRawValue.replace(/,/g, '.')) || 0;
  // Format back to comma-separated with € symbol for display
  this.value = numericValue.toFixed(2).replace('.', ',') + '€';
};

// Clean the value to pure numeric before form submission
document.querySelector('form').addEventListener('submit', function(e) {
  const priceInput = document.getElementById('price');
  // Strip all non-numeric/dot characters and convert to valid float
  let backendFriendlyValue = parseFloat(priceInput.value.replace(/[^\d.-]/g, '')) || 0;
  // Set input to 2-decimal numeric string for backend parsing
  priceInput.value = backendFriendlyValue.toFixed(2);
});

Improved HTML Input (for Laravel/PHP Backends) #

Since you’re using old(), we can format the saved value correctly when repopulating the form:

<div class="form-group col-md-6">
  <label for="price">Price</label>
  <input type="number" min="1" step="any" required 
         value="{{ old('price') ? number_format(old('price'), 2, ',', '') . '€' : '0.00€' }}" 
         name="price" id="price" placeholder="Price (Ex: 10.00)"/>
</div>

This uses PHP’s number_format to convert the raw numeric value from the backend into the user-friendly comma-separated format with the € symbol.

2. Backend Validation (Critical—Don’t Trust Frontend!) #

Frontend validation can be bypassed, so always validate and clean data on the backend. Here’s how to do it with Laravel (since you’re using old()):

Laravel Validation Example #

// In your controller method
$validated = $request->validate([
    'price' => 'required|numeric|min:1', // Ensure it's a number ≥1
]);

// Clean to 2 decimal places (use bcadd for perfect precision instead of round if needed)
$cleanPrice = round((float)$validated['price'], 2);
// Or with bcmath for absolute precision:
// $cleanPrice = bcadd($validated['price'], '0', 2);

Raw PHP Validation Example #

If you’re not using a framework:

$price = $_POST['price'] ?? '';

// Validate the input
if (!is_numeric($price) || (float)$price < 1) {
    $_SESSION['errors']['price'] = "Please enter a valid price of at least 1";
    header("Location: your-form-page.php");
    exit;
}

// Clean to 2 decimal places
$cleanPrice = round((float)$price, 2);

3. Database Storage (Avoid Float Precision Issues!) #

Never use FLOAT or DOUBLE for currency—these types have binary precision errors that will mess up your prices over time. Instead, use a fixed-precision decimal type.

MySQL Example #

Define your price column like this:

price DECIMAL(10, 2) NOT NULL

• 10 = total number of digits (9 for integer part + 2 for decimals)
• 2 = number of decimal places
  This supports prices from 0.00 to 99999999.99, which covers most use cases.

When inserting/updating, just pass the $cleanPrice value directly—no formatting needed.

4. Key Best Practices #

• Precision First: Always use decimal types for currency storage to avoid rounding errors.
• Frontend is for UX, Backend is for Security: Frontend formatting makes input easier, but backend validation ensures data integrity.
• Localization Flexibility: If you need to support different regions (e.g., dot vs comma decimal separators), adjust frontend formatting based on user locale, but keep storage consistent as a decimal value.

内容的提问来源于stack exchange，提问作者user9607361