Saadav

Write like a pro: Hello saadadv! Sorry for that. Just seen the conversation. Apologies again it was late here now about 4.00 am. I see your problem with rocket lms p ayment gateway. This can be fixed since It was working before but I need mire details to review. Can I get the link to your site so I can assess type error on front end. Also the fixing will involve accessing the root files so when that time come you will provide access credentials. For now If you can give me the link I would check that on front end and advise.

ChatGPT said:

Sure! Here’s a more professional and polished version of your message:

---

Subject: Follow-Up on Rocket LMS Payment Gateway Issue

Hello saadadv,

Apologies for the delay—I’ve just seen the conversation, and it’s currently around 4:00 AM on my end.

Regarding the issue with the Rocket LMS payment gateway, I understand your concern. Since it was functioning correctly before, I’m confident this can be resolved. However, I’ll need a bit more information to properly assess the issue.

Could you please share the link to your site? I’d like to review the front-end behavior and identify any visible errors. Once I’ve had a look, I’ll provide further guidance.

Please note that resolving this may require access to the root files, so when we get to that stage, I’ll request the appropriate credentials.

Looking forward to your response.

Best regards,
[Your Name]

You said:

Mention it wa late here but am online..

ChatGPT said:

Subject: Follow-Up on Rocket LMS Payment Gateway Issue

Hello saadadv,

I apologize for the delayed reply—it was quite late here (around 4:00 AM), but I’m now online and ready to assist.

Regarding the issue with your Rocket LMS payment gateway: since it was functioning properly before, I’m confident we can get it working again. To diagnose the problem, I’ll need a few more details.

Could you please share the URL of your site so I can review the front-end behavior and identify any visible errors? Once I’ve had a look, I’ll advise on the next steps. Fixing this issue may require access to your root files, so when the time comes, I’ll ask for the necessary credentials.

Thank you, and I look forward to your response.

Best regards,
[Your Name]
[Your Position]
[Company Name]
[Contact Information]

You said:

The coomunicationwa done 2 hours ago…it was late then now its 4am…renove the subject..this is a message plain text

ChatGPT said:

Thought for a couple of seconds

Hello saadadv,

I’m sorry I didn’t respond earlier—our last message was sent about two hours ago, and it was already quite late here. It’s now around 4:00 AM, but I’m online and ready to help.

I understand you’re having trouble with the Rocket LMS payment gateway. Since it was working before, I’m confident we can resolve the issue. To start, could you please share the link to your site so I can review the front end and identify any visible errors? Once I’ve taken a look, I’ll advise on the next steps.

Please note that fixing this may require access to your root files, so when the time comes, I’ll ask for the necessary credentials.

Thank you, and I look forward to your response.

Best regards,
[Your Name]
[Your Position]
[Company Name]
[Contact Information]

You said:

wrie like a pro: Could you send the site link. I am checking from there first. Though after all ftp wont be sufficient, I need full root access to files and database….but thta’s later. Send me the site link and what p ayment gateway are you using?

ChatGPT said:

Thought for 8 seconds

Hello [Name],

Could you please share the link to your site? I’ll begin by reviewing the front end there. While FTP access may help, it won’t be sufficient for a full resolution—I’ll eventually need full root access to the files and database. Also, please let me know which payment gateway you are using.

Thank you,
[Your Name]

You said:

Explain the error from TaPayment Gateway

ChatGPT said:

Thought for 8 seconds

The “Error : 1164” you’re seeing is coming straight from Tap’s API. According to Tap’s official error list, 1164 means “Merchant id is invalid”—in other words, the gateway is rejecting your request because the merchant credentials you’re sending don’t match any active Tap account. developers.tap.company

Concretely, this usually happens when:

1. The merchant ID (or secret key) in your configuration is mistyped
   • Double-check that the value of TAP_SECRET_KEY (and/or TAP_PUBLIC_KEY) in your .env or configuration file exactly matches what Tap provided in your dashboard.
   • Remember that Tap’s sandbox and live environments each have their own keys; using a live key against the sandbox endpoint (or vice versa) will often trigger error 1164.
2. You’re calling the wrong environment endpoint
   • If your Laravel package is pointing to https://api.tap.company/v2/ but you only provided sandbox credentials (or you’re pointing to the sandbox URL with live credentials), Tap will not recognize your merchant ID and return 1164.
3. The merchant account has been disabled or is not fully activated
   • Log in to Tap’s merchant portal and confirm that the account associated with that merchant ID is active and in good standing. If your account is still pending verification or has been suspended for any reason, the same “invalid merchant” response will be returned.

---

How to Resolve

1. Verify Your Keys/IDs
   • Open your Tap dashboard → go to Settings → API Credentials.
   • Copy the merchant ID (secret key) exactly, without extra spaces or line breaks, and paste it into your Laravel .env (e.g. TAP_SECRET=https://…).
   • Likewise, confirm that TAP_PUBLIC_KEY and any other “source” or “platform” identifiers match precisely.
2. Check Environment URLs
   • In your PaymentChannels/Drivers/TapPayment/Channel.php (or wherever your package config lives), ensure you are calling the correct base URL for your credentials.
     • Sandbox (Test) URLs typically look like https://api.sandbox.tap.company/v2/…
     • Production (Live) URLs are https://api.tap.company/v2/…
   • If you’re testing locally, use your sandbox keys against the sandbox endpoint. If you’re ready to go live, switch to production keys and the production URL.
3. Confirm Account Status
   • Log in to Tap’s merchant portal and verify your account is fully activated (no pending tasks, no requirement to upload extra documents). An unverified or suspended merchant will also trigger “invalid merchant” errors.

Once the merchant ID (and secret key) match the correct environment, the 1164 error will disappear and your payment requests should proceed normally.

Sources

You said:

Just writer a few sentences to ask the client to do as a first check

ChatGPT said:

Hello [Client Name],

As a first step, could you please log in to your Tap dashboard and verify that the merchant ID and secret key in your configuration exactly match the values shown there? Also confirm whether you’re using sandbox keys against the sandbox endpoint (or live keys against production). Once you’ve double-checked those details, let me know and we can proceed with further troubleshooting.

Thank you.

You said:

Add them

ChatGPT said:

Please copy the exact values from your Tap dashboard into those two fields:

• secret_api_key → Use your live secret key if you’re in production (e.g.
  sk_live_RZ9N2IAE8pOJWlcx7uBQien4), or your test secret key if you’re in sandbox mode (e.g.
  sk_test_Zd3gzV7a2R0qjpSYQkwJbXEm).
• merchant_id → 36869302

Make sure there are no extra spaces or line breaks when you paste. Once those match exactly, the gateway should authenticate successfully.

You said:

Update the .env with the credentials

ChatGPT said:

Below is an example of how your .env file should look once you’ve inserted the Tap credentials exactly as shown in your dashboard. Be sure to replace any existing Tap-related lines with the following (no extra spaces or quotes):

dotenvCopyEdit# TapPayment Gateway Configuration
TAP_SECRET_KEY=sk_live_RZ9N2IAE8pOJWlcx7uBQien4
TAP_MERCHANT_ID=36869302

If you ever need to switch to Sandbox/Test mode, simply replace the above with your test keys:

dotenvCopyEdit# TapPayment Gateway (Sandbox/Test)
TAP_SECRET_KEY=sk_test_Zd3gzV7a2R0qjpSYQkwJbXEm
TAP_MERCHANT_ID=36869302

Once you’ve saved these changes:

1. Clear your configuration cache: bashCopyEditphp artisan config:clear
2. Verify that your application is pointing at the correct Tap endpoint (sandbox vs. live) in your payment driver.

With these values in place and the config cache cleared, Tap should authenticate successfully (no more “Error 1164”).

You said:

how to download databae from ftp

ChatGPT said:

Thought for a couple of seconds

Below is a straightforward, step-by-step guide to retrieving your database via FTP. Because FTP itself only transfers files (and databases live inside MySQL/MariaDB), this guide assumes one of two scenarios:

1. Scenario A: You (or your host) have already created a database dump (e.g., a .sql or .zip file) on the server, and you just need to download it via FTP.
2. Scenario B: No dump exists yet, so you first need to export (dump) the database to a file, then download that file via FTP.

---

Scenario A: Download an Existing Database Dump via FTP

If your server already contains a SQL dump (for example, database_backup.sql or site_db_2025-06-04.zip), here’s how to pull it down:

1. Install or Open Your FTP Client

• Windows/macOS/Linux: We’ll use FileZilla for this example, but any FTP/SFTP client (WinSCP, Cyberduck, Transmit, etc.) works the same way.
• If you don’t already have one, download and install FileZilla Client, then open it.

2. Gather Your FTP Credentials

You’ll need:

• Host (Server Address): e.g. ftp.yourdomain.com (or an IP address like 123.45.67.89).
• FTP Username: provided by your host (e.g. ftp_user1).
• FTP Password: the password that goes with that user.
• Port: usually 21 for plain FTP or 22 for SFTP (SSH-based transfer). Confirm with your host which protocol and port to use.

If you’re not sure, check your hosting control panel or ask your system administrator.

3. Connect to the Server

1. Open FileZilla.
2. At the top, you’ll see fields for Host, Username, Password, and Port.
3. Enter them exactly, then click Quickconnect.
4. If it’s your first time connecting, FileZilla may warn you about the server’s certificate (for SFTP) or “unknown certificate” (for FTPS). Verify that it matches what your host provided, then click OK to proceed.

Once connected, FileZilla’s left pane shows your local computer’s files, and the right pane shows the remote server’s file structure.

4. Locate the Database Dump on the Server

• In the Remote Site (right-hand) pane, navigate to the folder where your host places backups or dumps. This might be named something like:
  • /backups/
  • /database/
  • /home/ftp_user1/backups/
  • /home/ftp_user1/datadumps/
  (The exact path depends on how your host organizes backups. If you aren’t certain, check with your hosting documentation or support.)
• Look for a file with a name resembling: pgsqlCopyEditmydatabase_YYYY-MM-DD.sql mydatabase_backup.sql site_db_2025-06-04.zip Common extensions are .sql, .sql.gz, or .zip. Once you locate that file, you’re ready to download.

5. Download the File to Your Local Machine

1. In the Remote pane, click on the database dump file you want (e.g. mydatabase_2025-06-04.sql).
2. Drag it from the right pane into a folder on your Local Site (left pane). For example, drag it into C:\Users\YourName\Downloads\ or ~/Documents/Backups/.
3. FileZilla will begin transferring the file. In the bottom panel you can watch the progress.
4. Wait until the transfer completes (100% in the “Successful transfers” tab). The file is now on your local computer.

Tip: If the dump is large (many hundreds of megabytes), ensure you have enough local disk space and a stable internet connection. If the connection drops, you can resume the transfer in FileZilla—right-click the partially downloaded file and choose “Resume” when reconnecting.

That’s it. You’ve successfully downloaded an existing database dump from the server via FTP.

---

Scenario B: Create a New Database Dump, Then Download It via FTP

If you don’t yet have a .sql or compressed dump on the server, you need to export your MySQL/MariaDB database first. Below are two common ways:

1. Via cPanel/phpMyAdmin (web interface).
2. Via SSH/Command Line (if you have shell access).

Once you have the dump file in your home directory (or a designated backups folder), you then follow Scenario A above to FTP-download it.

Method 1: Export Using phpMyAdmin (via cPanel or Similar)

1. Log in to your Hosting Control Panel (e.g., cPanel, Plesk, or another custom dashboard).
2. Look for phpMyAdmin or MySQL Databases → phpMyAdmin. Click it.
3. Once phpMyAdmin opens, select the database you want from the left sidebar.
4. Click the Export tab at the top.
5. Choose the Quick export method and SQL format, then click Go.
6. Your browser will instantly download a .sql file (e.g., mydatabase.sql). If phpMyAdmin forces a small download rather than placing it in a server folder, skip the FTP step—phpMyAdmin has already given you the file. Note: If the database is very large (100 MB+), phpMyAdmin might time out or produce a partial dump. In that case, use the SSH method below.

Method 2: Export via SSH with mysqldump

If you have SSH access to your server:

1. SSH into Your Server bashCopyEditssh [email protected]
2. Run mysqldump bashCopyEditmysqldump -u db_username -p db_name > ~/mydatabase_$(date +%F).sql
   • Replace db_username with your MySQL user.
   • Replace db_name with the name of the database.
   • You will be prompted for your MySQL password.
   • The output file will be placed in your home directory (e.g. /home/your_ssh_user/mydatabase_2025-06-04.sql).
3. (Optional) Compress the Dump bashCopyEditgzip ~/mydatabase_$(date +%F).sql This creates mydatabase_2025-06-04.sql.gz which is much easier to download if the database is large.
4. Confirm the File Exists bashCopyEditls -lh ~/*.sql* You should see something like: cssCopyEdit-rw-r--r-- 1 your_ssh_user your_ssh_user 75M Jun 4 03:45 mydatabase_2025-06-04.sql.gz

5. Download the Dump via FTP

1. Open FileZilla (or your preferred FTP client).
2. Connect using the same FTP credentials described in Scenario A.
3. In the Remote Site pane, navigate to your home directory where the dump now lives (e.g. /home/your_ssh_user/). If you compressed it, you’ll see mydatabase_2025-06-04.sql.gz.
4. Drag the .sql or .sql.gz file from the right pane down into a local folder in the left pane.
5. Wait for FileZilla to complete the transfer.

---

Quick Recap

1. If a dump already exists:
   • Use FileZilla (or any FTP client) to connect, locate the .sql (or .zip/.gz) in your backup folder, and download it to your computer.
2. If no dump exists yet:
   1. Via phpMyAdmin: Export → Quick → SQL → Download immediately.
   2. Via SSH:
      • mysqldump -u db_user -p db_name > ~/mydatabase.sql
      • (Optional) gzip ~/mydatabase.sql → mydatabase.sql.gz.
   3. Then follow Step 1 of “If a dump already exists” to FTP-download that newly created file.

---

Tips & Troubleshooting

• FTP vs. SFTP
  • Always prefer SFTP (port 22) if your host supports it—a secure, encrypted connection.
  • If you only have plain FTP (port 21), be aware that credentials and data are transferred unencrypted.
• Large Files
  • If your .sql is over ~100 MB, consider compressing it first (.gz). Otherwise, the FTP transfer might be slow or unstable.
  • On shared hosting, you may need to split a very large dump into chunks—tools like split or plugins like “WP-DB-Backup” can help.
• Permissions
  • Make sure the directory where you place your dump (e.g. ~/) is world-readable by your FTP user. Otherwise, you might see “Permission denied” when browsing via FTP.
  • If necessary, chmod 644 ~/mydatabase.sql.gz to ensure it’s readable.
• Verify Integrity
  • After downloading, open the .sql (or decompress the .gz) and scroll to the bottom to confirm it ends with something like /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;. If it stops abruptly, it may have timed out—redo the dump in smaller chunks or compress first.

---

With these steps, you can reliably export and download your database via FTP. If you run into any errors (“connection timed out,” “file not found,” or “permission denied”), double-check:

1. The path where the dump lives (ensure you’re in the correct directory).
2. That your FTP user has access to that folder.
3. That you’re using the correct host/username/password/protocol (FTP vs SFTP).

Once you have the .sql or .sql.gz file on your local machine, you can import it elsewhere (e.g., a local MySQL instance, another server, or a development environment).

You said:

where on laravel?

ChatGPT said:

Thought for a few seconds

In a default Laravel setup, there is no actual “.sql” or database file sitting inside your project folder—you’re connecting to a separate MySQL/MariaDB (or PostgreSQL, etc.) server. In other words, Laravel does not store the raw database in app/, resources/, public/, or any other directory. Instead, Laravel merely holds your connection credentials (in .env) and talks to the database engine.

---

1. Understanding Why You Won’t “Find” a Database File in Laravel

• Laravel’s Database Configuration Lives in .env
  Open your project’s root and inspect the .env file. You’ll see something like: envCopyEditDB_CONNECTION=mysql DB_HOST=127.0.0.1 DB_PORT=3306 DB_DATABASE=your_database_name DB_USERNAME=your_db_username DB_PASSWORD=your_db_password This tells Laravel how to connect to the database, but it does not keep a copy of it in the codebase.
• The Actual Data Is in MySQL, Not in Your Laravel Folders
  When your application runs, Eloquent/Query Builder executes SQL against the MySQL server specified above. If you want to “grab” or download that data, you must export (dump) it from MySQL itself—Laravel won’t automatically generate a .sql to include in your Git or FTP directory.

---

2. How to Generate (and Then FTP-Download) a Database Dump for a Laravel App

Since there is no built-in .sql inside Laravel, you need to create one first. Below are the two most common approaches:

A. Use MySQL’s mysqldump via SSH

If you have SSH (shell) access to the same server where Laravel is hosted, do this:

1. SSH into Your Server bashCopyEditssh [email protected] (Replace your_ssh_user and your.server.domain with your actual server credentials.)
2. Navigate (optional) to a “Backups” Folder
   Often, administrators will keep dumps in a dedicated directory. For example: bashCopyEditcd ~/backups If that directory doesn’t exist, you can stay in your home directory (~), or create a folder like ~/db_backups.
3. Run mysqldump Using the Credentials from Your .env
   First, open your Laravel project and copy the relevant values from .env: envCopyEditDB_DATABASE=your_database_name DB_USERNAME=your_db_username DB_PASSWORD=your_db_password DB_HOST=127.0.0.1 # or “localhost” or another host DB_PORT=3306 Now execute: bashCopyEditmysqldump \ -h 127.0.0.1 \ -P 3306 \ -u your_db_username \ -p your_database_name \ > ~/backups/laravel_db_$(date +%F).sql
   • After hitting Enter, you’ll be prompted for the MySQL password (whatever is in DB_PASSWORD).
   • This command creates a file named, for example, laravel_db_2025-06-04.sql in ~/backups.
4. (Optional) Compress the Dump
   If your database is large, you can gzip it: bashCopyEditgzip ~/backups/laravel_db_$(date +%F).sql You’ll end up with laravel_db_2025-06-04.sql.gz, which is much smaller to transfer over FTP.
5. Verify the Dump Exists bashCopyEditls -lh ~/backups/laravel_db_*.sql* You should see something like: cssCopyEdit-rw-r--r-- 1 your_ssh_user your_ssh_user 52M Jun 4 10:12 laravel_db_2025-06-04.sql.gz
6. Disconnect from SSH bashCopyEditexit
7. Use FTP/SFTP to Download
   • Open your FTP client (FileZilla, Cyberduck, WinSCP, etc.).
   • Connect to the same server using your FTP/SFTP credentials.
   • Navigate (in the Remote Site panel) to ~/backups (or wherever you placed the dump).
   • Drag the laravel_db_2025-06-04.sql.gz (or .sql) to a folder on your local computer.
   • Wait for the transfer to finish.

Now you have a complete SQL dump of your Laravel application’s database on your local machine.

---

B. Use phpMyAdmin (If cPanel or a Web‐Based Control Panel Is Available)

If you do not have SSH, many hosts provide phpMyAdmin for database management. To export via phpMyAdmin:

1. Log in to cPanel or Your Hosting Control Panel
   – Look for phpMyAdmin under “Databases.”
2. Open phpMyAdmin and Select Your Database
   – On the left sidebar, click the database name that matches DB_DATABASE from your .env (e.g., your_database_name).
3. Go to the “Export” Tab
   – Click Export in the top menu.
4. Choose “Quick” and “SQL”
   – Under “Export method,” leave Quick selected.
   – Under “Format,” choose SQL.
   – Click Go.
5. Download the File
   – phpMyAdmin will immediately download a file called something like your_database_name.sql to your local computer.
   – If the file is very large, phpMyAdmin might time out. In that case, you’ll either need to export in smaller chunks (partial tables) or ask your host for a server‐side dump.
6. (Optional) Compress the Downloaded Dump
   – If phpMyAdmin gave you a plain .sql, you can gzip or zip it locally if you want to save space.

Since phpMyAdmin downloads directly to your local machine, there is no separate “FTP” step. If you do need to store it on the server first, use the same “Upload” area in cPanel to place it in a known directory, then connect via FTP to grab it.

---

3. Summary

• Laravel does not store a .sql file inside app/ or database/. It simply holds the connection settings in .env.
• To “grab” your database, you must create a dump via either:
  1. SSH & mysqldump (preferred for large databases).
  2. phpMyAdmin Export (easier if you lack SSH).
• Once the dump exists on the server (e.g., ~/backups/laravel_db_2025-06-04.sql), connect via FTP/SFTP and download that file to your local machine.

By following these steps, you’ll have a complete export of your Laravel app’s database—ready for local development, backups, or migration.

You said:

has plesk got php myadmin

ChatGPT said:

Yes—Plesk bundles phpMyAdmin (or an equivalent database browser) for managing MySQL/MariaDB databases. Here’s how to find and open it:

1. Log in to Plesk
   • Open your browser and navigate to your Plesk panel (e.g. https://your‐server:8443).
   • Enter your admin (or user) credentials.
2. Go to “Websites & Domains” → “Databases”
   • In the left sidebar, click Websites & Domains (or simply Domains, depending on your Plesk version).
   • Under that domain’s row, click the Databases icon.
   • You’ll see a list of all databases associated with that subscription (e.g. yourapp_db, wordpress_db, etc.).
3. Click the “phpMyAdmin” (or “WebAdmin”) Button
   • Locate the database you want to inspect.
   • In the same row, look for a small “phpMyAdmin” button (sometimes labeled “WebAdmin (phpMyAdmin)”).
   • Click that icon. Plesk will open phpMyAdmin in a new tab or window.
4. Use phpMyAdmin as Usual
   • Once inside phpMyAdmin, you can browse tables, run SQL queries, export (export → Quick → SQL), import, and perform all standard database operations.
   • If you need to export a full .sql dump:
     1. Select the database name in the left column.
     2. Click the Export tab at the top.
     3. Choose Quick – display only the minimal options, ensure SQL is selected, then click Go.
     4. Your browser will download a .sql file containing the entire database.

---

If You Don’t See “phpMyAdmin” in Plesk

• Check User Role/Permissions:
  • Some Plesk user roles (for instance, a limited “Database‐only” user) may not show the phpMyAdmin button. Make sure you’re logged in as the subscription owner or an administrator with database‐management rights.
• Plesk Version Differences:
  • On older Plesk versions, the database manager might be called “WebAdmin for MySQL” or “Adminer” instead of phpMyAdmin. The steps are identical—click that button next to your database, and you’ll be dropped into the built‐in database GUI.
• Enable phpMyAdmin in Plesk Settings (if missing):
  1. Go to Tools & Settings (in the left sidebar).
  2. Under Tools & Resources, click Database Servers.
  3. Select your MySQL/MariaDB server and ensure phpMyAdmin is installed/enabled. If the checkbox (or toggle) for phpMyAdmin is turned off, re‐enable it and save.

Once phpMyAdmin (or its equivalent) is enabled and you have the proper permissions, the “phpMyAdmin” icon will appear next to each database entry under Websites & Domains → Databases. Clicking that gives you full, familiar access to view, export, or modify your database contents.

You said:

where is phpmyadmin?

ChatGPT said:

Thought for a few seconds

In recent Plesk versions, phpMyAdmin (or “WebAdmin” for MySQL/MariaDB) is accessed per-database rather than as a global button on the first “Databases” screen. Here’s how to find it:

1. Log in to Plesk and click Databases in the left sidebar.
   • You’ll see a list of subscriptions (e.g. “li.sa,” “koshkatglobal.com,” etc.), not the raw database names.
2. Drill down into the subscription that owns your database
   • On that “Databases” page, click the subscription name (for example, li.sa).
   • Now you’ll see a list of actual database entries (e.g. li_sa_db, or whatever your DB is called).
3. Look for the “WebAdmin” (phpMyAdmin) icon next to the database name
   • In that subscription’s database list, each row shows:
     • Database name (e.g. li_sa_database)
     • Type (MySQL or MariaDB)
     • “Webadmin” or phpMyAdmin button/icon (usually a small “ 🗄️ ” or “phpMyAdmin” text) on the right.
   • Click that WebAdmin/phpMyAdmin icon to open the database management interface in a new tab.
4. If you still don’t see a WebAdmin/phpMyAdmin button
   • You may have to scroll the table horizontally; sometimes it’s hidden off to the right.
   • Confirm that the database actually exists under that subscription. If there’s no database name listed at all, you might need to create or assign one first.
   • Check Tools & Settings → Database Servers and ensure phpMyAdmin (or “WebAdmin for MySQL”) is installed/enabled. If it’s disabled, toggle it on and click OK.
   • Make sure your Plesk user has sufficient permissions (e.g. “Database management” rights) to see and open phpMyAdmin.

Once you click the WebAdmin/phpMyAdmin icon, you’ll be dropped into phpMyAdmin (in a new browser tab), where you can browse tables, run SQL queries, or export (dump) the database.