Laravel Conditional Queries

### Example Scenario
You want to search for a record that matches a specific condition. If no such record is found, a different fallback query should run. Here’s how you can achieve this:

### Using Eloquent

use AppModelsYourModel;

// Search for a specific condition
$result = YourModel::where('column', 'value')->first();

if (!$result) {
    // Fallback query if no match is found
    $result = YourModel::where('other_column', 'default_value')->get();
}

### Using Query Builder

use IlluminateSupportFacadesDB;

// Search for a specific condition
$result = DB::table('your_table')->where('column', 'value')->first();

if (!$result) {
    // Fallback query if no match is found
    $result = DB::table('your_table')->where('other_column', 'default_value')->get();
}

### Advanced: Combine in a Single Query (SQL Case Statement)
If your use case permits, you can combine the logic in a single query using a `CASE` statement. However, this might not be as flexible as separate queries.

$result = YourModel::selectRaw("
    CASE 
        WHEN EXISTS(SELECT 1 FROM your_table WHERE column = 'value') 
        THEN (SELECT id FROM your_table WHERE column = 'value') 
        ELSE (SELECT id FROM your_table WHERE other_column = 'default_value') 
    END as result
")->get();

### Explanation
– **Eloquent `where` Query**: Checks for the specific condition.
– **Fallback Logic**: Runs another query if the initial one doesn’t return results.
– **Combined Query (Optional)**: Uses SQL to decide based on the availability of a match.

Would you like an optimized solution for a specific scenario?

### Example Scenario
You have multiple keywords and want to search for records that match any of them in a column (e.g., a "name" column).

—

### Using `where` with Multiple Keywords

use AppModelsYourModel;

// Keywords to search
$keywords = ['keyword1', 'keyword2', 'keyword3'];

$query = YourModel::query();

foreach ($keywords as $keyword) {
    $query->orWhere('column', 'LIKE', "%{$keyword}%");
}

// Get the results
$results = $query->get();

This approach creates a query like:

SELECT * FROM your_table WHERE column LIKE '%keyword1%' OR column LIKE '%keyword2%' OR column LIKE '%keyword3%';

—

### Using `whereIn` for Exact Matches
If you're looking for exact matches of multiple keywords:

$keywords = ['keyword1', 'keyword2', 'keyword3'];

$results = YourModel::whereIn('column', $keywords)->get();

This translates to:

SELECT * FROM your_table WHERE column IN ('keyword1', 'keyword2', 'keyword3');

—

### Searching Across Multiple Columns
If you want to search multiple columns with multiple keywords:

$keywords = ['keyword1', 'keyword2', 'keyword3'];

$query = YourModel::query();

$query->where(function ($q) use ($keywords) {
    foreach ($keywords as $keyword) {
        $q->orWhere('column1', 'LIKE', "%{$keyword}%")
          ->orWhere('column2', 'LIKE', "%{$keyword}%");
    }
});

// Get the results
$results = $query->get();

—

### Using Full-Text Search (Optimized for Large Data)
If your database supports full-text search (e.g., MySQL's `MATCH`), you can use it for better performance:

$keywords = 'keyword1 keyword2 keyword3';

$results = YourModel::whereRaw("MATCH(column) AGAINST(? IN NATURAL LANGUAGE MODE)", [$keywords])->get();

This is more efficient for large datasets with proper indexing.

—

### Combining Search with Fallback Logic
If you want to perform a fallback query when no results are found:

$keywords = ['keyword1', 'keyword2', 'keyword3'];

$results = YourModel::where(function ($query) use ($keywords) {
    foreach ($keywords as $keyword) {
        $query->orWhere('column', 'LIKE', "%{$keyword}%");
    }
})->get();

if ($results->isEmpty()) {
    // Fallback query
    $results = YourModel::where('fallback_column', 'default_value')->get();
}

—

### Optimizing Queries
– **Indexes**: Ensure the columns you're searching have proper indexes for better performance.
– **Pagination**: Use `->paginate()` instead of `->get()` for large datasets.
– **Full-Text Search**: Use if available for large datasets.

Let me know if you need further help implementing these solutions!

—

### 1. **Check the Manifest File**
The Vite manifest file (`public/build/manifest.json`) should have an entry for `resources/css/app.css`. Open the file and ensure the entry exists:

{
    "resources/css/app.css": {
        "file": "css/app.[hash].css"
    }
}

If the entry is missing, it suggests the CSS file was not included during the Vite build process.

—

### 2. **Verify the CSS Import**
Ensure you are importing the CSS file in your `resources/js/app.js` (or equivalent entry file) as follows:

import '../css/app.css';

This is necessary for Vite to recognize and process the CSS file during the build.

—

### 3. **Run the Vite Build Command**
Run the following command to rebuild your assets:

npm run build

or, if using Yarn:

yarn build

Then, check if the manifest file includes the `resources/css/app.css` entry.

—

### 4. **Clear Laravel Cache**
Laravel might be caching outdated references to the manifest. Clear the cache:

php artisan optimize:clear

—

### 5. **Serve Assets in Development Mode**
If you're in development mode and the issue persists, ensure Vite's dev server is running:

npm run dev

Also, verify that `VITE_DEV_SERVER_URL` in your `.env` file is correctly set to your local development server URL (e.g., `http://localhost:5173`).

—

### 6. **Check Your Vite Config**
Open `vite.config.js` and verify that the `input` configuration includes `resources/css/app.css`:

import { defineConfig } from 'vite';
import laravel from 'laravel-vite-plugin';

export default defineConfig({
    plugins: [
        laravel({
            input: ['resources/js/app.js', 'resources/css/app.css'],
            refresh: true,
        }),
    ],
});

—

### 7. **Permissions Issue**
Ensure the `public/build` directory and its files have the correct permissions:

chmod -R 775 public/build

—

### 8. **Verify the Environment**
Check your environment setup:
– In **development**, the CSS file should be served dynamically by Vite.
– In **production**, ensure the `npm run build` process successfully generated the CSS file in `public/build`.

—

### 9. **Debug the Manifest**
If everything seems correct but the error persists, you can manually inspect or log the manifest contents in your Blade template:

@php
    dd(json_decode(file_get_contents(public_path('build/manifest.json')), true));
@endphp

This will help you confirm whether `resources/css/app.css` is present and correctly mapped.

—

Let me know if you still encounter issues after these steps!

—

### 1. **Revalidate Vite Input Configuration**
Since you have Vue files in `resources/js` and a separate admin section in `resources/views/admin`, make sure your `vite.config.js` includes **all relevant inputs**, especially `resources/css/app.css`:

import { defineConfig } from 'vite';
import laravel from 'laravel-vite-plugin';

export default defineConfig({
    plugins: [
        laravel({
            input: [
                'resources/js/app.js', 
                'resources/css/app.css', 
                'resources/js/admin.js' // Add other entry points if needed
            ],
            refresh: true,
        }),
    ],
});

Make sure the CSS file is explicitly listed in the `input` array.

—

### 2. **Verify CSS Import in JavaScript**
Confirm that the CSS file is imported in your Vue application's main entry point, usually `resources/js/app.js`:

import '../css/app.css';

Without this import, Vite won’t know to process the CSS file.

—

### 3. **Regenerate the Manifest**
Delete the existing build files and regenerate them to ensure Vite includes all specified inputs.

1. Delete the `public/build` directory:

rm -rf public/build

2. Rebuild assets:

npm run build

—

### 4. **Inspect the Manifest**
After building, check the contents of `public/build/manifest.json` to ensure `resources/css/app.css` is listed. You should see something like this:

{
    "resources/css/app.css": {
        "file": "css/app.[hash].css"
    }
}

If it’s not present, something is preventing the file from being included in the build.

—

### 5. **Ensure Blade Template References Are Correct**
If you’re loading `resources/css/app.css` dynamically in your Blade template, ensure the following code is used:

@vite('resources/css/app.css')

This will fetch the CSS path from the manifest.

—

### 6. **Check for Dev/Prod Environment Mismatch**
If you’re running the app in development mode, ensure the Vite dev server is active:

npm run dev

Then confirm your `.env` file has the correct `VITE_DEV_SERVER_URL`:

VITE_DEV_SERVER_URL=http://localhost:5173

In production, ensure the build process runs and serves static files from `public/build`.

—

### 7. **Debugging Tips**
– **Log the Manifest in Blade**: Add this snippet to your Blade view to debug:

@php
      dump(json_decode(file_get_contents(public_path('build/manifest.json')), true));
  @endphp

– **Look for Errors in Console**: Check the browser console for any errors related to loading the CSS file.

—

### 8. **Ensure File Permissions**
Ensure the `public/build` directory and its files are readable by the web server:

chmod -R 775 public/build

—

### 9. **Confirm Node and Vite Versions**
Ensure you’re using compatible versions of Node.js, Vite, and Laravel Vite Plugin:
– Node.js: Latest stable version (as you're already on Node.js 21).
– Vite Plugin: Ensure it’s up to date in your `package.json`.

Update dependencies if necessary:

npm install

—

If the issue persists after these steps, let me know the output of your `manifest.json` and the specific error message!