We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation states
Blueprint supports all of the available column types within Laravel.
but it fails to correctly define a geography in the database migrations
models: Location: name: string:100 description: nullable text coordinates: geography,points
Which creates a string for coordinates instead of a $table->geography
$table->geography
Schema::create('locations', function (Blueprint $table) { $table->id(); $table->string('name', 100); $table->text('description')->nullable(); $table->string('coordinates');
instead of
Schema::create('locations', function (Blueprint $table) { $table->id(); $table->string('name', 100); $table->text('description')->nullable(); $table->geography('coordinates', 'point');
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Issue:
Documentation states
but it fails to correctly define a geography in the database migrations
draft.yaml:
Which creates a string for coordinates instead of a
$table->geography
instead of
The text was updated successfully, but these errors were encountered: