Hello, are you planning to add a xml type?

Laravel doesn't support ENUM type for postgres. It declares it as a VARCHAR with constrain which is not very convenient.  Can we have ENUM support at this great library?

I'm having an issue getting migrations to work with this package.

The problem seems to be a class loading issue, but I'm not 100% sure. Here's what my migration file looks like:

use Bosnadev\Database\Schema;
use Bosnadev\Database\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;

class TestMigration extends Migration
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::create('test', function(Blueprint $table)
        {
            $table->engine = "InnoDB";

                $table->increments('id');
            $table->uuid('public_uid');
            $table->uuid('private_uid');

            $table->softDeletes();
            $table->timestamps();
        });
    }

    /**
     * Reverse the migrations.
     *
     * @return void
     */
    public function down()
    {
        Schema::drop('test');
    }
}

Here's the error I get when trying to migrate:

[ErrorException]                                                                                                                                                                              
  Argument 1 passed to TestMigration::{closure}() must be an instance of Bosnadev\Database\Schema\Blueprint, instance of Illuminate\Database\Schema\Blueprint given, called in /Users/mydir/LaravelProjects/laravel5/vendor/illuminate/database/Schema/Builder.php on line 132 and defined

I'm hoping other users, or @mirzap might be able to help me troubleshoot this issue. Thanks!

Using Postgres timestamp with time zone column with Laravel causes an issue with Carbon

InvalidArgumentException in Carbon.php line 414:
Trailing data

This is because the data returned by Postgres include the +00 timezone information on the end. One fix would be to override getDateFormat and have it return 'Y-m-d H:i:sO' but of course we'd only want to do that where timezones are being used.

Models can override their own dateFormat property, but pivot tables with timestamps can't do this (since there's no actual model for them).

[ErrorException]
Declaration of Bosnadev\Database\Connectors\ConnectionFactory::createConnection() should be compatible with Illuminate\Database\Connectors\ConnectionFa
ctory::createConnection($driver, $connection, $database, $prefix = '', array $config = Array)

Laravel Version: 8.48.1
PHP Version: 8.0.1

Migrations that mix integer() (or bigInteger()) with unsigned() no longer migrate, but throw an error with Postgres error.

Schema::create('broken_primary', function (Blueprint $table) {
    $table->integer('broken_id')->unsigned()->primary();
    $table->timestamps();
});

You are loading BaseTestCase in prod, but there does not seem to be a need to. I want to move it to the -dev autoload. I am about 5 min from making a PR. I just wanted an issue number to reference.

This is causing us an issue as we strip "tests" from vendor folders when pushing to prod servers to make the transfer as small as possible. Since you are loading that file from the test folder in prod, then composer dies for us.

I have grep'ed through the code & only see references to it from files in the test folder, so I am hoping that this will be a non-issue & we can make the change.

Thanks for your time & work on this package.

When using useCurrent in a migration:

$table->dateTime('intCreatedDateTime')->useCurrent();

This throws the error:

   TypeError 

  preg_match(): Argument #2 ($subject) must be of type string, Illuminate\Database\Query\Expression given

  at vendor/bosnadev/database/src/Bosnadev/Database/Schema/Grammars/PostgresGrammar.php:300

Is this a known issue? Thanks for your help.

plz add support for uuid ^4

Hey, I included your stuff per autoload in my Laravel project (installing via composer and vcs doesn't work). It seems to boot nicely though I still get an error when using the new types in my migrations like $table->uuid('id') Please, could you guide me through how to set it up correctly or how it's intended to be included in a laravel project?

Any plans to support Laravel 6?

When I try to run composer update with bosnadev/database": "^0.11.0 I get

Problem 1
    - The requested package bosnadev/database could not be found in any version, there may be a typo in the package name.

910ecf3 has changed PostgresGrammar.php line 62 and 75. Due to this, is null queries (all queries in a model with soft delete) are throwing column not found error.

Would it be possible to support doctrine/dbal 3?

"doctrine/dbal": "^2.5|^3.0"

This repository feels abandoned - nothing has been done in ages and support for modern versions of Laravel is not being implemented.

I have forked the repository at https://github.com/BrekiTomasson/database and updated it to support Laravel 10. I will continue to maintain the project until @bosnadev tells me otherwise. If I have not heard from him in the next couple of months, I will consider the project to be abandoned and will release my fork officially.

Helo,
When we can expected laravel 9 support ?

Does this package support Laravel 8x?