Skipper support site - Recent questions

Possible to update revision when exporting?

Thu, 14 Nov 2024 14:15:25 +0000

My setup is that I have a testing environment which runs via its own database and all tests are seeded as-is-needed on each test run. Therefore it's a clean database and there is no need to worry about updating the migrations data inline with a database.

This seems like the most sane way of doing this but it requires a button click for each time you export in order to update the migration, which of course needs to be always the very latest one anyway.

Is it possible to configure this? If not I think it would be a fairly common use-case so an option to configure this would be welcomed.

How to export with latestOfMany() relationships for hasOne?

Mon, 11 Nov 2024 15:31:23 +0000

I am exporting my project to a test environment and it is copying over all the models exported by Skipper as expected. I am using Laravel and so far everything is going well.

In order to not change the workflow I need to define latestOfMany() as the relationship default behaviour in the exported Abstract Model.

Is there something I'm missing, can you define such behaviour in Skipper?

Many thanks

Licence reset on each start

Tue, 04 Jun 2024 08:28:16 +0000

Hello,

Everytime I launch Skipper, I have to enter my Licence again and again.

I am using v3.3.5.

Thank you for your help.

Error on numerics with custom decimals after update to 3.3.7 | Laravel 9

Wed, 03 Apr 2024 12:27:20 +0000

I have a field with type decimal and decimal set to 3.

before update:
$table->decimal('weight', 8, 3)->nullable(true)->after('value')->change();

after update:
$table->decimal('weight', 3)->nullable(true)->after('value')->change();
error:

Numeric value out of range: 1264 Out of range value for column 'weight' at row 300 (SQL: ALTER TABLE amounts CHANGE weight weight NUMERIC(3, 2) DEFAULT NULL)

Doctrine3 Support

Tue, 26 Mar 2024 14:38:29 +0000

Dear All,

What date do you plan to support Doctrine 3?

I am starting to migrate my applications to PHP 8.3 and Doctrine 3 and I do not have support in Skipper18, I would like to have support soon so as not to waste time writing my own script to migrate to Doctrine 3

Thank you

Custom field options are not populated in Doctrine2 JoinColumn

Mon, 18 Sep 2023 06:06:31 +0000

All fields under Field Proprties are allowed to have options->comment added, that is saved in DDL via Doctrine's [options: comment="..."] mapping. While it would be nice if the "Description" also populated comment in the DDL, this isn't the biggest problem.

With a Many-to-One association added in the Associations tab a new field, say "pt_id", will be added in Field Properties tab. However, adding text in options => comment does not populate [options: comment="..."] in #[JoinColumn] but only for #[Column].

Strange table name

Fri, 04 Aug 2023 16:36:34 +0000

Hello,

I designed a Laravel Eloquent ORM with Skipper. I have an Entity named SourceDB.
When I export to ORM I have :
- Models are named SourceDB
- Migration create a datatable named source_dbs

But when I want to seed my database with the model, Laravel raise an error :

   Illuminate\Database\QueryException
  SQLSTATE[42S02]: Base table or view not found: 1146 Table 'testdb.source_d_b_s' doesn't exist (Connection: mysql, SQL: insert into `source_d_b_s` (`server_id`, `name`, `updated_at`, `created_at`) values (1, MyDB, 2023-08-04 13:13:13, 2023-08-04 13:13:13))

"Import External Model" with MySQL not using proper port?

Fri, 04 Aug 2023 16:36:31 +0000

I am running two instances of MySQL on my machine, one on port 3306 one in 3400. When I try to import the model from the 3400 instance, the connection is still being attempted with 3306 even with the proper setting in the dialog.

Is this a known issue?

Laravel Model and Migration Reconcile

Wed, 14 Jun 2023 14:27:57 +0000

Often, I make changes to models and migrations on the fly while coding. I try to remember to go back into Skipper and duplicate these changes, but it would be nice if there was a tool within Skipper that would update a project by reconciling models and migrations updated/added outside of Skipper. If this tool was created, I'd expect that the skipper format would have to be strictly followed and the tool would reject updated/added models and migrations when it wasn't. Just a thought.

Thanks,
Stephen

[Fixed] Index lenghts is not as expected

Fri, 02 Jun 2023 12:21:23 +0000

I am experiencing an issue with your tool, specifically concerning the generation of the index length attribute option. The generated output is not as expected.

I need this

[ORM\Index(name: "array", columns: ["array"], options: ["lengths"=>[100]])]

If i put [100] the result is:

[ORM\Index(name: "array", columns: ["array"], options: ["lengths"=>"[100]"])]

Skipper Linux x64 consuming huge amounts of VRAM using mutter-x11-frames

Thu, 11 May 2023 15:02:39 +0000

I've noticed that Skipper is consuming huge amounts of VRAM when open for several hours with the following config:

Skipper AppImage Linux
Ubuntu 23.04 with GNOME 44
X11
2560x1440@165Hz@100%

Output of nvidia-smi - you can clearly see mutter-x11-frames consuming >3GB VRAM

Thu May 11 16:54:57 2023       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 525.105.17   Driver Version: 525.105.17   CUDA Version: 12.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  Off  | 00000000:01:00.0  On |                  N/A |
| N/A   53C    P0    34W / 115W |   5197MiB / 16384MiB |      3%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      7922      G   /usr/lib/xorg/Xorg               1006MiB |
|    0   N/A  N/A      8177      G   /usr/bin/gnome-shell              258MiB |
|    0   N/A  N/A      8194      G   ...libexec/mutter-x11-frames     3380MiB |
|    0   N/A  N/A      8565      G   .../usr/bin/telegram-desktop       57MiB |
|    0   N/A  N/A      9345      G   ...veSuggestionsOnlyOnDemand       79MiB |
|    0   N/A  N/A      9403      G   ...RendererForSitePerProcess       35MiB |
|    0   N/A  N/A     10826      G   ...993402366275824947,131072       74MiB |
|    0   N/A  N/A     11110      G   ...b/thunderbird/thunderbird      171MiB |
|    0   N/A  N/A     12386      G   ...features=BackForwardCache       63MiB |
|    0   N/A  N/A     39624      G   /usr/bin/nautilus                  11MiB |
|    0   N/A  N/A     49680      G   ...RendererForSitePerProcess       28MiB |
|    0   N/A  N/A    165800      G   /usr/bin/gjs                       24MiB |
+-----------------------------------------------------------------------------+

[Fixed] Annotation export comment line length limit

Thu, 27 Apr 2023 12:55:39 +0000

Is there a way to force skipper to not reformat multi line annotation to single line?
Auto generated annotation sometimes is to long and does not pass phpcs, and every time I do export, skipper overwrite already formatted annotation to single line.

[Closed] Model Import from non standard MySQL port not working?!

Mon, 27 Mar 2023 05:53:29 +0000

Let's try this again... I asked this a week ago, but the question was never reviewed and doesn't show up in my questions...

Is this a known issue?

[solved] removing entity

Mon, 13 Feb 2023 11:12:51 +0000

Deleting an entity causes ORM export to complain about missing UUID. Is this not supported?
I am restructuring data and need to remove some entities.

Are skipper able to create has many through relations?

Tue, 07 Feb 2023 15:32:52 +0000

Is there a way to define hasmanythrough realtions in skipper?
https://laravel.com/docs/9.x/eloquent-relationships#has-many-through

/Frode

Changing VirtualAs generates illegal migration

Wed, 01 Feb 2023 10:20:04 +0000

If I need to change a concat value for a VirtualAs column, Skipper generates a migration that fails: 'Changing the STORED status' is not supported for generated columns'

Instead this column should be deleted and added?

If not, how do I recover from this without having to break my earlier migrations?

[solved] Wrong type hinting property name on polymorphic association (Laravel)

Tue, 31 Jan 2023 11:06:27 +0000

When exporting the models of a polymorphic association the property name is wrong. The skipper internal EntityAlias is correct

abstract class AbstractCompany extends Model
//the relation
public function documents()
{
return $this->morphMany('\App\Models\Document', 'documentable', 'documentabletype', 'documentableid');
}

//the wrong type hint
* @property \Illuminate\Database\Eloquent\Collection $company

//the right type hint should be
* @property \Illuminate\Database\Eloquent\Collection $documents

[Answered] Manually create migrations

Thu, 20 Oct 2022 16:19:03 +0000

I have a rather complex Skippermodel from a earlier project. I want to import into a fresh Laravel project..

Is there a way to tell Skipper that some models already have migrations?
Like users, passwordresets and failedjobs are tables created by a fresh Laravel project, so I want these models omitted when I export to ORM. But I want the models in skipper, so I can link relations to them.

/Frode

defining indexes in Table attribute doesn't work, I have to use Index attribute instead

Tue, 13 Sep 2022 16:00:42 +0000

this way of defining indexes seem not to be working

#[ORM\Table(
    name: 'custom_article_table_name',
    indexes: [
        new ORM\Index(name: 'name_index', columns: ['name'])
    ]
)]

I had to convert it to

#[ORM\Table(name: 'custom_invoice_table_name')]
#[ORM\Index(name: 'date_index', columns: ['date'])]

bug documentation to reproduce
https://gitlab.com/idlab-public/doctrine-attribute-index-bug

I don't know if this is a bug in Doctrine or the implementation of indexes:... is not fully supported in attributes arguments ?

All I have found is people fixing it with #[ORM\Index] attributes

https://stackoverflow.com/questions/73038623/why-doctrine-migrations-ignore-my-index-declaration

https://stackoverflow.com/questions/72744338/doctrine-migration-created-by-symfonymakerbundle-tries-to-remove-existing-indexe

Find a way for PHP attribute generator to match Symfony coding standards

Mon, 05 Sep 2022 09:48:36 +0000

In our quality tools, we enforce respecting Symfony's coding standards by runnig PHP CS fixer with one rule set : https://cs.symfony.com/doc/ruleSets/Symfony.html

When running CS fixer on Skipper generated Entities with attributes, the fixer alters the attributes on 4 different rules (see bellow).

When running Skipper generation again, the attributes are regenerated with Skipper's rules.

example of the "issue"

Skipper generated :

#[ORM\Table(name: "table_1",
        options: [
            "comment"=>"Long comment multiline",
            "row_format"=>"XY"
        ])]

#[ORM\Table(name: "table_2",
        options: ["comment"=>"Short comment","row_format"=>"XY"])]

PHP CS fixer "fixes" :

#[ORM\Table(name: 'table_1',
        options: [
            'comment'   => "Long comment multiline",
            'row_format'=> 'XY',
        ])]


#[ORM\Table(name: 'table_2',
        options: ['comment'=>'Short comment', 'row_format'=>'XY'])]

Propositions

A. Add a configuration to Skipper to run a post-generation script per Entity passing the Class as argument, like this

$ php vendor/bin/php-cs-fixer fix src/Entity/Person.php

B. Add a configuration to setup Skipper to respect the 4 rules bellow

Rules for reference

single_quote
https://cs.symfony.com/doc/rules/string_notation/single_quote.html

whitespaceaftercommainarray
https://cs.symfony.com/doc/rules/array_notation/whitespace_after_comma_in_array.html

trailingcommain_multiline
https://cs.symfony.com/doc/rules/control_structure/trailing_comma_in_multiline.html

binaryoperatorspaces
https://cs.symfony.com/doc/rules/operator/binary_operator_spaces.html

Side quest A

targetEntity could probably use ::class constant instead of explicit FQDN

#[ORM\ManyToMany(targetEntity: "App\Entity\Stakeholder\Organization", mappedBy: 'activities')]

could probably be replaced by

#[ORM\ManyToMany(targetEntity: Organization:class, mappedBy: 'activities')]

given the namespaces matches or the related entity is imported
but I am not sure about it and haven't tested it for now.

*To be honest, it is PHP Rector who proposed this fix when it ran it with this config https://getrector.org/blog/how-to-upgrade-annotations-to-attributes

Side quest B

named arguments order should match parameters order

Example:

#[ORM\ManyToMany(targetEntity: Organization:class, mappedBy: 'activities')]

should be

#[ORM\ManyToMany(mappedBy: 'activities', targetEntity: Organization:class)]

according to \Doctrine\ORM\Mapping\OneToMany::__construct

new OneToMany($mappedBy, $targetEntity, $cascade, $fetch, $orphanRemoval, $indexBy)

Php 8 attributes errors

Wed, 17 Aug 2022 07:19:49 +0000

Hi everyone.
I just tried the attributes export, and here are my notes :

Options for column have dots instead of arrows, and option name should be in "" : options: [unsigned: true] instead of options: ["unsigned" => true]

Same for DiscriminatorMap, exemple :

#[ORM\DiscriminatorMap([
    1: "App\Entity\AdresseEmailContact",
    2: "App\Entity\AdresseEmailEstimation",
    3: "App\Entity\AdresseEmailFacturation"
])]

When it should be arrows, like an array : 1 => "App\Entity\AdresseEmailContact"

For indexes, it seems that it's better to don't have it in the Orm\Table definition.

Example :

#[ORM\Table(name: "adresse_email_contact",
 indexes: [ORM\Index(name: "IDX_EC25E562FADC9094", columns: ["depot_vente_id"])])]

When this is totally working fine :

#[Orm\Table(name: "adresse_email_contact")]
#[Orm\Index(columns: ["depot_vente_id"], name: "IDX_EC25E562FADC9094")]

Same with unique constraints.

Another point is, it seems onUpdate is missing in the doctrine option attributes, don't know why.

That's all for the moment !

Regards.

One-to-one relation is converted to one-to-many when opening relation editor after file is closed and re-opened

Wed, 17 Aug 2022 07:19:45 +0000

Steps to reproduce
see https://www.dropbox.com/s/k1280enbubzwwuo/skipper-one-to-one-editor-bug.mov?dl=0
1. Create a new Skipper file
2. Create 2 Entities
3. Create 1 one-to-one relation
4. Save file
5. Close file
6. Re-open file
7. double-clic on relation
8. do not change anything
9. --> Cardinality is now "one-to-many"
10. Clic "Cancel"
11. --> User is prompted changes will be discarded (there are no changes

infos
3.2.35.1768
Version 1.0, build date/time (2021-09-07 22:38:43)
Skipper for mac 64-bit (73464)
Mac OS X 10.15.7

Doctrine Attributes dublicating skipper beta

Mon, 01 Aug 2022 08:59:07 +0000

After exporting doctrine schemas adding redundant ORM attribute. See below;
#[ORM, ORM, ORM, ORM, ORM, ORM, ORM\Id, ORM\Column(type: "integer"), ORM\GeneratedValue(strategy: "AUTO")] private ?int $id = null;

it repeats adding ORM any time export.

#[ORM, ORM]
#[ORM, ORM, ORM]
#[ORM, ORM\Id, ORM\Column(type: "integer"), ORM\GeneratedValue(strategy: "AUTO")]
private $id;

Odd Maintenance Warning After Beta Load in May

Tue, 28 Jun 2022 12:46:42 +0000

A few weeks after loading a "beta-patch" to correct an issue I reported concerning imported table fields being out of order, there is now an odd maintenance warning popping up when I open the app. There doesn't appear to be any action buttons in the message window, nor can I find a way to "check for updates" within the app. Should I just download and re-install with the latest version?

( See screenshot below and this thread: https://www.skipper18.com/support/4165/possible-laravel-eloquent-maintains-currently-alphabetical )

Are there any plans for supporting TypeORM?

Wed, 18 May 2022 12:32:16 +0000

I've used Skipper for a few years, but stopped after moving towards JavaScript development. I'm now starting to integrate TypeORM into one of my projects and at first glance I see many similarities with Doctrine. It would be very nice to see this JS ORM framework integrated in Skipper. If so, I would certainly use Skipper again!

use skipper with eloquent and phinx

Fri, 13 May 2022 17:55:54 +0000

For a new project I need to use the SLIM4 framework instead of my trusted laravel. I have added Eloquent and will do migrations through phinx (from cakephp).
I want to use skipper for databases design, ORM class generation and migration. I almost got it working but two thing are still giving me trouble:

the generated filename for migrations are of a form that phinx does not understand, and I can't find a way to make it more succeptible. skipper generates yyyymmddtttttt{name}.php but phynx does not recognise this file, it needs yyyymmddtttttt_{name}.php. Is there any way to set the output filename format for migration files?
the migration class (use top of migration file) is fixed at Illuminate\Database\Migrations\Migration. In my case that needs to be \Migration\Migration which is the class that extends the phinx abstract mygration class. Is there any way to setup the template(?) skipper uses?

all the best!
Michael

[fixed] Is it possible to do a Laravel/Eloquent MySQL ORM import that maintains field order (currently alphabetical)

Mon, 09 May 2022 19:56:32 +0000

When I import a Laravel/Eloquent ORM through a connection to MySQL, the entities all list the fields in alphabetical order instead of the order in which the fields are listed in the actual DB table. Is there a way to achieve this with the current version? If not, I'd like to make that a feature request.

Thanks,
Stephen Dukes

Setting key / index length

Thu, 24 Mar 2022 08:39:51 +0000

Hi,

MySQL 5.6 and Amazon Aurora have a max key length of 767 bytes. Because one character uses 4 bytes when using utf8mb4 charset, that means an index can only be created for max 191 chars. So even creating an index on a VARCHAR(255) field will fail with the error message: #1071 - Specified key was too long.

The only way to index such fields is either by reducing the field's size to 191 or by limiting the index/key length to 191.

Defining the field size in Doctrine is possible since 2.9 (see https://github.com/doctrine/dbal/pull/2412).

Can you please add an option to set the key length in Skipper? Exporting to entities should be pretty straightforward. E.g.: @Index(name="indexname", columns={"columnname"}, options={"lengths": {191}})

Thanks very much!

[Closed] Skipper not working with php8 annotation syntax

Thu, 24 Feb 2022 15:11:06 +0000

How to import project with php 8 annotation syntax. it seems, that skipper cannot find any entities when im trying to import symfony 6 project with doctrine2

my entity already in project:

import result:

[Solved] how to import with php8 annotation in symfony 6 project

Sat, 19 Feb 2022 14:00:17 +0000

hi, getting no entity found with import of symfony 6 project and php 8 annotation

[Closed] Can't copy file... Error: boost::filesystem::copy_file: Invalid argument

Thu, 03 Feb 2022 07:34:31 +0000

After updating to a newer version I can't save or update anymore as both give error on file copy. I'm on version 3.2.35.1759 and I also tried manually downloading the latest version, but it has the same problems.

Saving fails when it tries to copy the project file to a .bak file and updating fails when it tries to copy platforms/libqxcb.so to a backup folder. Both give out same error message (only with different file paths):

*** Unhandled Atomix exception
*** Qt information:
Error <boost::exception> sending event 11QMouseEvent to object  (11QToolButton)
*** Exception information:
axCore/axFileSystem/helpers/fileHelper.cpp(131): Throw in function static bool Atomix::CFileHelper::CopyFile(axPath, axPath)
Dynamic exception type: boost::wrapexcept<Atomix::CException>
std::exception::what: std::exception
exception_message: Can't copy file [/path/to/MyProject.skipper] to [/path/to/MyProject.skipper.bak]. Error: boost::filesystem::copy_file: Invalid argument: "/path/to/MyProject.skipper", "/path/to/MyProject.skipper.bak"

File permissions are not the issue, old version of Skipper worked fine with same files. Also, it does create the file it is trying to copy to, only it's left empty.

After Googling for the error message, found some discussion in another programs github issues about boost being "quite fragile, sensitive to quirks of platform dependence and various file systems" and there were talk about it not working on encrypted filesystem. I am on Linux and I have encrypted home folder, so I tried saving the project file outside my home directory and then it works without errors. Never had any problems with any other software regarding the encrypted home directory and I have been using it for many years, and even the old version of Skipper was working just fine. Hope you can fix this quickly, currently can't really use it at all as I can't save any changes.

Does Skipper run on MacOS Monterey?

Thu, 13 Jan 2022 21:31:02 +0000

Before I upgrade to Monterey, it would be helpful to know if I will lose my favorite data modeling tool for Symfony-Doctrine.

Unique Constraint and Doctrine Table Name Error

Tue, 11 Jan 2022 07:19:18 +0000

Hello,

I have two entities in which I have created a Unique Constraint index. One table has a field called emailAccount . When I export to ORM and doctrine imports the Entity it creates the column as email_account. When the Annotations are created I get the following line

@ORM\Table(uniqueConstraints={@ORM\UniqueConstraint(name="TenantUniqueEmail", columns={"emailAddress","tenant_id","id"})})

emailAccount doesnt exist as a column name so I have to manually modify the file to state email_address. Is this expected behavior, or is there a way I can modify a config to include the table name and not the entity name?

Is this more of an issue with Doctrine?

Thanks for any help you have.

Seth

[Closed] Is it possible to export Doctrine configuration with Attributes

Wed, 24 Nov 2021 21:34:39 +0000

Is there any way to export Doctrine entity classes configured with Attributes instead of Annotations?

https://www.doctrine-project.org/projects/doctrine-orm/en/2.10/reference/attributes-reference.html

If not, is this feature planned soon?

SSH Tunnel for MySQL Import and Navicat Support

Fri, 19 Nov 2021 22:21:28 +0000

I would like to pull down the schema for all my projects, but they all require an SSH tunnel to access (without replicating them all). My go-to MySQL client is Navicat which has SSH tunnel capability; so, having support for SSH tunnels, Navicat, or both would help me out a lot.

Great product btw. Thanks!

How to do references with mongodb odm?

Tue, 14 Sep 2021 20:57:35 +0000

I'm new to skipper but i managed to work with ORM with success; but now i need to design ODM entities in mongodb and i can't figure out how to make the references between entity fields as shown here:
https://www.doctrine-project.org/projects/doctrine-mongodb-odm/en/2.2/reference/reference-mapping.html

thanks!

Laravel Doc Block property types

Sun, 29 Aug 2021 18:05:39 +0000

Hey guys - so the doc block comments don't work property for a few types.

In Skipper when you select a UUID column, that should always be cast to a string.

In Skipper, you select a timestamp but in Laravel that would be considered a \Carbon\Carbon instance, and even added to the "dates" array over the casts array. The doc comments say "timestamp" which isn't a valid type and does not support autocomplete features. This forces us to overwrite the type in the parent model.

Example would be:

@property \Carbon\Carbon $created_at

Not sure the best way to handle this on your end, but maybe provide an option to have a custom doc block cast type in Skipper so if you're making use of a custom caster of sorts, that would make it easy to just provide the actual class name which would be referenced in the blocks...

Toggle foreign key generation

Tue, 17 Aug 2021 06:11:02 +0000

Possibly an edge case, but I am working on a large-scale migration where we need to keep a legacy database running whilst upgrading parts of it in phases to Laravel. Both databases will reside on the same server during this development.

We have been migrating a selection of tables at a time, and in one case we are looking at generating a temporary relationship between a table in the new database and a table in the legacy database.

See the 2 many-to-many relationships coming from Organisation below.

For LegacyUserHasOrganisation, I want the relationship definitions on the model, but I want to avoid physically setting the foreign keys on the legacy database.

I'm able to manually simulate this behaviour by commenting out the foreign key generation in the migration file, e.g.

// Schema::table('legacy_user_has_organisation', function (Blueprint $table) {
//     $table->foreign('organisation_id')->references('id')->on('organisations');
//     $table->foreign('user_id')->references('User_Id')->on('users');
// });

Does functionality like this already exist in Skipper, or can it be added in a future release?

Can I hide an entity from the graph

Fri, 18 Jun 2021 21:16:52 +0000

Hi
I have one central entity "Domain" that has a relation with just about all other tables.
Currently it's simply creating more lines in the graph than necessary. So I would like to hide that entity and its associations from the graph (the module...?) to clean it up. Is this possible. Or even better: is it possible to hide the associations of that particular entity?

[Fixed] Running xmllint against generated schema fails

Fri, 21 May 2021 14:33:51 +0000

When running xmllint against the generated schema there are several validation errors:

Skipper v3.2.32.1734
Doctrine ORM v2.8.5

Running

xmllint --noout --schema vendor/doctrine/orm/doctrine-mapping.xsd data/orm/Money.Money.dcm.xml

with the generated schema (data/orm/Money.Money.dcm.xml):

<?xml version="1.0"?>
<doctrine-mapping xmlns="http://doctrine-project.org/schemas/orm/doctrine-mapping" xsi="http://www.w3.org/2001/XMLSchema-instance" schemaLocation="http://doctrine-project.org/schemas/orm/doctrine-mapping.xsd">
  <embeddable name="Money\Money" class-type="embeddable">
    <field name="amount" type="bigint" nullable="false"/>
    <field name="currency" type="currency" nullable="false"/>
  </embeddable>
</doctrine-mapping>

Gives the following errors:

data/orm/Money.Money.dcm.xml:2: element doctrine-mapping: Schemas validity error : Element '{http://doctrine-project.org/schemas/orm/doctrine-mapping}doctrine-mapping', attribute 'xsi': The attribute 'xsi' is not allowed.
data/orm/Money.Money.dcm.xml:2: element doctrine-mapping: Schemas validity error : Element '{http://doctrine-project.org/schemas/orm/doctrine-mapping}doctrine-mapping', attribute 'schemaLocation': The attribute 'schemaLocation' is not allowed.
data/orm/Money.Money.dcm.xml:3: element embeddable: Schemas validity error : Element '{http://doctrine-project.org/schemas/orm/doctrine-mapping}embeddable', attribute 'class-type': The attribute 'class-type' is not allowed.
data/orm/Money.Money.dcm.xml fails to validate
warning: failed to load external entity "2"

The corrected XML validates:

<?xml version="1.0"?>
<doctrine-mapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                  xmlns="http://doctrine-project.org/schemas/orm/doctrine-mapping"
                  xsi:schemaLocation="http://doctrine-project.org/schemas/orm/doctrine-mapping
                          https://www.doctrine-project.org/schemas/orm/doctrine-mapping.xsd">
    <embeddable name="Money\Money">
        <field name="amount" type="bigint" nullable="false"/>
        <field name="currency" type="currency" nullable="false"/>
   </embeddable>
</doctrine-mapping>

The formatting I can deal with, but is there any way to remove/correct the invalid attributes and update to the correct XML header?

[Solved] PHP 8 Union Types Unsupported

Thu, 20 May 2021 17:44:29 +0000

The following fatal exception is thrown when exporting a model which has at least one property declared with a PHP 8 union type:

 Invalid variable character[|], different than $

Project Info:
- Doctrine 2
- No ORM
- Export Data Format: Doctrine2 Annotations

Minimum reproduction example:

<?php

use Doctrine\ORM\Mapping as ORM;

/**
 * @ORM\Entity
 */
class SampleEntity
{
    /**
     * @ORM\Id
     * @ORM\Column(type="integer")
     * @ORM\GeneratedValue(strategy="AUTO")
     */
    private $id;

    /**
     * @ORM\Column(type="string", length=255, nullable=true)
     */
    private $test;

    private string|null $example = null;

    public function getTest(): ?string
    {
        return $this->test;
    }

    public function getExample(): ?string
    {
        return $this->example;
    }
}

Import laravel migrations

Wed, 12 May 2021 06:08:12 +0000

Hello,

I have Laravel+Postgress project and I would like to import migrations to the Skipper to see visualisation of schema.

I tried Import existing project -> Laravel -> Laravel -> Database -> Postgres -> Connection settings OK -> In the root path I selected Laravel project root path.

After import I have message:

And nothing imported.
Could you please help to solve this ?

Thank you very much in advance.

[Closed] ubuntu 20.01

Thu, 06 May 2021 13:25:13 +0000

[solved] Skipper in dark mode

Tue, 20 Apr 2021 10:09:24 +0000

Hi, I'm using skipper with macOS Catalina in dark mode. The error messages in skipper look like this:

Can I change the background or font color somewhere?

Thank you.

[Fixed] Update document generation to avoid deprecation notices of doctrine/mongo-db-odm

Tue, 23 Mar 2021 14:03:51 +0000

doctrine/mongo-db-odm logs the following deprecation notices:

1) Since doctrine/mongodb-odm 2.1: The "boolean" mapping type is deprecated. Use "bool" instead.

2) Since doctrine/mongodb-odm 2.2: The "@Indexes" annotation used in class "App\Document\X" is deprecated. Specify all "@Index" and "@UniqueIndex" annotations on the class

Can you please have a look and adjust the document generation? Thanks!

[Implemented] Code hinting for properties on Laravel model

Mon, 22 Mar 2021 17:36:33 +0000

Hey everyone, i just wanted to say that one thing that has always been a pain is the time it takes to write out all the properties and model relationships into the code comments in order to get autocomplete in your IDE's.

I would imagine that this could be a very simple task for skipper to handle this because all of the relationships are already being defined for you.

Would it be too much to ask for the function return methods to show the proper relationships, and the abstract models to list out all the columns on the database along with their types?

/**
* @property int $id
* @property string $the_thing
* @property \Carbon\Carbon $created_at
* @property \Carbon\Carbon $updated_at
* @property \App\Models\Relation $relation
*/

That type of stuff would be super helpful and save us countless hours of typing :)

[Closed] How to clear internal Sqlite data structure inconsistency

Sat, 20 Mar 2021 06:29:03 +0000

Hello,

I can't remember when it was happened, it seems Skipper's internal data has been collapsed.
When I try to add a index to some entities, I get error like:

Sqlite get data next row failed (1)
Query:
INSERT INTO [IndexField]([uid],[uuid],[tmpDirtyFlag],[index_id],[field_id],[ownerProject_id]) VALUES (6008,'b1a9ca0f-8ea6-4cc0-b26d-f02c912b6ad6',1,24,847,1);

I can add indexes if I edit Skipper's XML file directly, but this error persists.

Is there any way to "reset" internal data structure?

[Closed] illuminate eloquent support without laravel

Fri, 05 Feb 2021 21:35:08 +0000

I have some ideas on you can make skipper more useful if you are open to hear it.

First I am using CI3 as a framework. It is outdated and the creators have left CI 3 users without a path to upgrade to CI4.

I started using illuminate eloquent in my project to get more modern ORM features. It has been great.

I am able to use skipper to get a jump on the creation of the models, but with a lot of manual modification. Mostly done with rename utilities and also some python scripts.

I think it is good, but it would be much nicer if I had more control over what was generated.

For example, I setup my name space as Models;

This way all the illuminate eloquent models won't interfere with everything else. I also don't really like having abstract models and then normal models. My models aren't so large I can't just use them directly. If we had the ability to change the name space and imports and also using abstract classes or not I think it would make it so I can use skipper without doing any additional modifications. I understand why you would use abstract models when using a generator though, but since my use case is more of a 1 time setup it doesn't make as much sense.

Normally I just create my models as I go now, but still using skipper is a nice thing to have just to stay up to date and look at how everything is progressing. I first used skipper like a year ago.

So if you can, please give more ability to customize a Laravel like environment using Eloquent but maybe not Laravel as a whole.

I want to use laravel and maybe some time down the line the project will be completely converted, but until then it requires much more work on my part.

I know using Eloquent as a stand alone package is pretty popular. I even use schema builder as well for migrations although wrapped in some CI3 controllers specific to CI3 migrations. For example.

<?php

use Illuminate\Database\Capsule\Manager as Capsule;
use Illuminate\Database\Schema\Blueprint;

class Migration_PeoplePhone_authorized_add extends CI_Migration {
  private $table = "person_phones";

  public function __construct() {
      parent::__construct();
  }

  public function up() {
    if(Capsule::schema()->hasTable($this->table)) {
      Capsule::schema()->table($this->table, function (Blueprint $table) {
        $table->boolean('authorized')->after('receive_texts')->default(0)->comment('added in migration 037');
        $table->integer('authorization_code')->after('authorized')->nullable()->comment('added in migration 037');
        $table->dateTime('authorization_code_date')->after('authorization_code')->nullable()->comment('added in migration 037');
      });
    }
  }

  public function down() {
    if(Capsule::schema()->hasTable($this->table)) {
      $table_name = $this->table;
      Capsule::schema()->table($this->table, function (Blueprint $table) use ($table_name) {
        if (Capsule::schema()->hasColumn($table_name, 'authorized')) {
          $table->dropColumn('authorized');
          $table->dropColumn('authorization_code');
          $table->dropColumn('authorization_code_date');
        }
      });
    }
  }
}
?>

And the models look more like this

<?php
namespace Models;

class Person extends BaseModel
{
    /**  
     * The table associated with the model.
     * 
     * @var string
     */
    protected $table = 'people';

    /**  
     * Primary key name.
     * 
     * @var string
     */
    public $primaryKey = 'person_id';

    /**  
     * Do not automatically manage timestamps by Eloquent
     * 
     * @var bool
     */
    public $timestamps = false;

    /**  
     * The attributes that should be cast to native types.
     * 
     * @var array
     */
    protected $casts = [
        'person_id' => 'integer',
        'organization_id' => 'integer',
        'person_type_id' => 'integer',
        'primary_site_id' => 'integer',
        'title' => 'string',
        'given_name' => 'string',
        'given_middle_name' => 'string',
        'family_name' => 'string',
        'email' => 'string',
        'address_1' => 'string',
        'address_2' => 'string',
        'address_3' => 'string',
        'city' => 'string',
        'state' => 'string',
        'postal_code' => 'string',
        'country_id' => 'integer',
        'extra_1' => 'string',
        'created_at' => 'datetime',
        'created_by' => 'integer',
        'conversion_id' => 'string'
    ];

    public function organization()
    {
        return $this->belongsTo(Organization::class, 'organization_id', 'organization_id');
    }

    public function documentCategories()
    {
        return $this->hasMany(DocumentCategory::class, 'person_id', 'person_id');
    }

    public function documents()
    {
        return $this->hasMany(Document::class, 'person_id', 'person_id');
    }

    public function employees()
    {
        return $this->hasMany(Employee::class, 'person_id', 'person_id');
    }

    public function eventPeoples()
    {
        return $this->hasMany(EventPerson::class, 'person_id', 'person_id');
    }

    public function groupPeoples()
    {
        return $this->hasMany(GroupPerson::class, 'person_id', 'person_id');
    }

    public function personPhones()
    {
        return $this->hasMany(PersonPhone::class, 'person_id', 'person_id');
    }

    public function users()
    {
        return $this->hasMany(User::class, 'person_id', 'person_id');
    }
}
?>

As you can see I also have a BaseModel that is the parent of all models that use a common set of functions. Being able to set this would also be nice.

I know some of these things are project specific, but thought I would show what I am using it for to see if you can improve things if it is useful.

Thanks, Ryein

[Fixed] How can you stop the "keyType" of the model from being a "bigInteger"?

Sat, 23 Jan 2021 17:54:29 +0000

This setting is throwing a fatal error because there's no such thing as a bigInteger cast in a laravel model. We are being forced to delete every $keyType property manually on every export. This isn't ideal. Am I doing something wrong in Skipper?

[Fixed] Dark mode export status unreadable

Wed, 20 Jan 2021 21:19:27 +0000

First of all, thank you for adding dark mode (dark theme). I have just one issue - when exporting entities the status column has white font (added by dark theme) on light green/red/yellow background which is totally unreadable. I personally know from years of using Skipper what the colors mean but someone might find that a bit confusing.