Skipper support site - Recent questions in Bug report

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)

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].

"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?

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 |
+-----------------------------------------------------------------------------+

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?

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

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 )

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

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...

Unique key definition with two columns gets exported as camelCase with db-naming-strategy: underscore-lower

Wed, 18 Dec 2019 13:39:06 +0000

Skipper Build 3.2.22.1624
Symfony 4.4.1
Doctrine ORM 2.7.0

I have a problem with our setup and combined unique keys. The column definition is exported "as-is" (with camelCase column names). But in our doctrine.yaml we have:

naming_strategy: doctrine.orm.naming_strategy.underscore_number_aware

The resulting export is:

* @ORM\Table(uniqueConstraints={@ORM\UniqueConstraint(name="CityUnique", columns={"city","countryCode"})})

which leads to the error:

$ php bin/console make:mig

In SchemaException.php line 82:

 There is no column with name 'countryCode' on table 'city'.

The db-naming-strategy on the index is set to underscore-lower, but to no effect.

Edit: I see, I have to set the db-naming-strategy on the Bundle! Then it's exported correctly. But shouldn't Skipper also consider the setting on index level? What does that do anyway?

Minimal working example:

<?xml version="1.0"?>
<skipper version="3.2.22.1624" mvc="Symfony" orm="Doctrine2" name="CombinedUniqueCasingBug" uuid="80e32f16-3bca-43a6-b0a9-a79e6031bcfd">
  <module name="\MainBundle" local-name="MainBundle" namespace="\" export-format="Doctrine2Php" export-path="." uuid="cd31ef60-361c-4fab-8296-1149aea063d9">
    <entity name="\City" local-name="City" namespace="\" uuid="23f6cc2f-c7eb-468b-bdbe-41959a0ac413">
      <field name="id" type="integer" required="true" unique="true" primary="true" auto-increment="true" uuid="1ffad554-fadb-4878-8002-f87248be9ea3"/>
      <field name="city" type="string" size="255" uuid="b37fe101-5b5e-4dbc-a255-455be0c5bc8b"/>
      <field name="countryCode" type="string" size="2" uuid="c94a2f4a-a5dd-49d2-920d-a7c5797d8425"/>
      <index name="CityUnique" unique="true" uuid="1259fd89-cfc2-4696-8460-78bafa55b28c">
        <index-field name="city" uuid="21ad701d-5071-4975-b735-a87ac0194c47"/>
        <index-field name="countryCode" uuid="fec6c53e-6663-4f7a-a7d7-5445e7c50106"/>
        <orm-attributes>
          <attribute name="db-naming-strategy">underscore-lower</attribute>
        </orm-attributes>
      </index>
    </entity>
  </module>
  <visual-data>
    <entity uuid="23f6cc2f-c7eb-468b-bdbe-41959a0ac413" bg-color="#FFFFFF" hdr-color="#D2D2D2" position-x="10" position-y="20"/>
    <module uuid="cd31ef60-361c-4fab-8296-1149aea063d9" bg-color="#FEFCE8" position-x="61" position-y="72" size-x="11" size-x2="220" size-y="22" size-y2="163"/>
    <project uuid="80e32f16-3bca-43a6-b0a9-a79e6031bcfd" size-x="0" size-x2="331" size-y="0" size-y2="285"/>
  </visual-data>
</skipper>

[Solved] cannot export to entities which include public static methods

Wed, 13 Nov 2019 16:44:09 +0000

Hi,
Since the latest update Skipper chrashes on export to entities which contain methods marked as "public static".
These methods are completly unrelatet to the properties which skipper should manage.

Ausnahmefehler bei 0x696484CB (ucrtbase.dll) in Skipper.exe: Schwerwiegende Beendigung des Programms angefordert

its means : exception... termination requested

How can this be fixed?
Thank you in advance.
Peter

[Fixed] “Skipper” can’t be opened because Apple cannot check it for malicious software.

Tue, 12 Nov 2019 09:55:47 +0000

On mac catalina 10.15.1 when the app is opened I get this message:

“Skipper” can’t be opened because Apple cannot check it for malicious software.

This software needs to be updated. Contact the developer for more information.

Chrome downloaded this file on 9 November 2019 from www.skipper18.com.

How can this be solved?

[Fixed] Exporting entity with class-type "trait" ignores the namespace

Mon, 14 Oct 2019 10:16:54 +0000

Doctrine2, export format: Annotations.
Generated PHP file misses the namespace clause. Neither bundle's nor entity's setting is used.

Starting a 2nd Skipper Instance raises a session restore question

Wed, 04 Sep 2019 08:26:42 +0000

I'm not sure if it's even officially allowed to start multiple Instances, but it's definitely possible.

When the second instance starts, a dialog box shown below appears:

The first instance doesn't crash and after skipping the restoration, the second instance works correctly too.

Warning message before updating to a new version of skipper that will not work on current OS...

Fri, 19 Jul 2019 03:32:34 +0000

I have just hit the update button on skipper while working on an urgent project and now I get this message:

Would it not be too much to ask to provide a warning, before update takes place that an OS is going to need to be updated as well?

What is the process to roll skipper back to an older version?

Skipper Changes Non-Entity Variables Annotations

Wed, 29 May 2019 13:39:47 +0000

Background

App: Skipper v3.2.19.1545
OS: xUbuntu 18.04, fully updated
ORM: Doctrine 2, annotations driver

Problem

Every time I try to export the model to the ORM some of my entities are changed in an unexpected way:

This change is made every time I correct it manually, and obviously the Skipper shouldn't touch code inside of the methods ;)

Index field names not generated as column names

Thu, 21 Sep 2017 15:49:25 +0000

Symfony3 framework, Doctrine2 ORM.

When exporting Entities that contain an constraint, the columns field in the Table annotation is populated with entity property names, not DB column names. This causes an error if the property names are camelCase and the column names are underscore_case.

In other words, this:

 @ORM\Table(uniqueConstraints={@ORM\UniqueConstraint(name="sns_recip", columns={"snsNotificationId","snsRecipient"})})

should be this:

@ORM\Table(uniqueConstraints={@ORM\UniqueConstraint(name="sns_recip", columns={"sns_notification_id","sns_recipient"})})

wrong extension in doctrine2 xml export

Fri, 07 Jul 2017 07:42:04 +0000

When I do a doctrine2 XML export, the extension of the files are yml.
Additional info: I changed a yml export to xml export.

YML export - Gedmo soft_deleteable has broken following a recent Skipper upgrade (3.2.10.1370)

Fri, 19 May 2017 16:05:06 +0000

Hi.

Other people have recently raised the issue of YML export being incorrect when it comes to outputting Gedmo behaviours. I am having a similar problem with SoftDeletable.

Before a recent upgrade to 3.2.10.1370, the YML was being generated correctly:

gedmo:
  soft_deleteable:
    field_name: deleted_at

But it's now exporting as

gedmo:
  - soft_deleteable:
      field_name: deleted_at

This has broken my entire project.

I tried to follow advice to go for XML export, but when I try that a number of my entities report "No identifier/primary key specified for Entity" when I'm using a primary key not called 'id'.

What's my best solution?

Thanks
Dave

Many-to-many relationship between 3 existing entities, create new columns (while they are already there)

Fri, 07 Apr 2017 15:45:00 +0000

Many-to-many relationship between 3 existing entities, the software will create new columns (while they are already there)

Hello,

When creating a many-to-many relationship between 3 existing entities, "already existing"!
If I select existing columns, the software will create new columns with "2" at the end of the column name (while they are already there) ...

Ps: the same process works for a one-to-many relationship (it does not create a new column and does not add "2" at the end of the column name)

thank you

the cmd+z crashes the software, when back creating associations

Fri, 07 Apr 2017 07:03:50 +0000

Hello,

There is a serious problem with the: cmd+z
It crashes the software ...
Especially during the back creation of associations:
(One-to-many OR many-to-many) + cmd+z = crash

thank you

Many to many created in corner top right

Fri, 24 Feb 2017 10:45:11 +0000

Hi,

I got an issue with visual editor happening only with ManyToMany button.

The issue is :
- I click on the "ManyToMany" button
- I click on my schema where i want to create it (let's say : in bottom left of my Bundle)
- I fill all fields required in the popin and i click "ok"

Then :
- The ManyToMany relation is correctly created BUT the entity is placed in the top right corner of the Bundle. Happens on all my project, only with ManyToMany relations but always with them.

My configuration : Skipper 3.2.8 / Mac OS 10.12.3

Thanks

Gedmo Sluggable does not support inherited fields

Wed, 19 Oct 2016 14:04:06 +0000

ORM Designer version 3.2.7.1338, MVC: Symfony3, ORM: Doctrine2

Sample project: https://support.skipper18.com/?qa=blob&qa_blobid=2312863847899793239

When I use the Gedmo Sluggable extension, I want to be able to select inherited fields as well. This is currently not possible in Skipper.

Expected output in SampleEntity:

/**
 * @ORM\Column(type="string", unique=true, length=255, nullable=false)
 * @Gedmo\Slug(fields={"firstName", "lastName"})
 */
private $name;

Doctrine2, Wrong "Embedded" property named "useColumnPrefix" (must be "columnPrefix" instead).

Thu, 01 Oct 2015 17:16:38 +0000

Using Doctrine DBAL 2.5.2 / ORM 2.5.1

@ORM\Embedded(class="DateRange", useColumnPrefix=false)

must be

@ORM\Embedded(class="DateRange", columnPrefix=false)