Alphanumeric Callsign For Flights (#1124)
* Alphanumeric Callsign For Flights PR adds ability to define alphanumeric callsigns to flights, display them and use them during SimBrief OFP generation (if pilot ident as callsign option is not enabled) Translations for en/es/it/pt-br added. * Change db table name * Change db column name, fix rules * Change db column name * Another db column name change * Just another one more * Last one from anumeric_callsign to callsign Co-authored-by: Nabeel S <nabeelio@users.noreply.github.com>pull/1127/head
parent
7502c053bf
commit
344edde0fb
@ -0,0 +1,30 @@
|
||||
<?php
|
||||
|
||||
use App\Contracts\Migration;
|
||||
use Illuminate\Database\Schema\Blueprint;
|
||||
use Illuminate\Support\Facades\Schema;
|
||||
|
||||
/**
|
||||
* Add a `anumeric_callsign` column for Alphanumeric Callsign to be assigned for a flight
|
||||
* Exp DLH78BF, THY8EA, OGE1978
|
||||
* According to FAA and EASA, callsigns must be maximum 7 chars in which first 3 chars is
|
||||
* airline ICAO code remaining rest can be used freely according to airline's choices
|
||||
*/
|
||||
class FlightsAddAlphanumericCallsign extends Migration
|
||||
{
|
||||
public function up()
|
||||
{
|
||||
Schema::table('flights', function (Blueprint $table) {
|
||||
$table->string('callsign', 4)
|
||||
->nullable()
|
||||
->after('flight_number');
|
||||
});
|
||||
}
|
||||
|
||||
public function down()
|
||||
{
|
||||
Schema::table('flights', function (Blueprint $table) {
|
||||
$table->dropColumn('callsign');
|
||||
});
|
||||
}
|
||||
}
|
Loading…
Reference in new issue