> For the complete documentation index, see [llms.txt](https://mostafaznv.gitbook.io/larupload/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mostafaznv.gitbook.io/larupload/advanced-usage/migrations/add-original-file-name-to-existing-tables.md).

# Add Original File Name to Existing Tables

<mark style="color:red;">\[</mark><mark style="color:red;">**Deprecated**</mark><mark style="color:red;">]</mark> As the <mark style="color:red;">{$name}\_file\_original\_name</mark> column has been added to Larupload since <mark style="color:red;">v2.2.0</mark>, you may need to add this specific column to your <mark style="color:red;">**existing**</mark> tables.

```php
<?php

use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;


return new class extends Migration
{
    public function up(): void
    {
        Schema::table('media', function (Blueprint $table) {
            $table->laruploadAddOriginalName('file');
        });
    }
};
```

{% hint style="info" %}
The first argument of `laruploadAddOriginalName` should match the first argument of `upload`.
{% endhint %}

{% hint style="info" %}
This column is only used when you've created table columns in HEAVY mode before.
{% endhint %}

{% hint style="danger" %}
This feature has been <mark style="color:red;">deprecated</mark> since version <mark style="color:red;">3.0.0</mark> and storing original file names is now enabled by default.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://mostafaznv.gitbook.io/larupload/advanced-usage/migrations/add-original-file-name-to-existing-tables.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.