Skipper support site - Recent questions and answers 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?

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

Tue, 27 Sep 2022 12:54:36 +0000

Hello,

new Skiper version with updated Attributes export for JoinColumn, InverseJoinColumn, JoinTable, Index, UniqueIndex is available for download.

Please test it and let me know if it solves all issues you had.

https://www.skipper18.com/support/402/downloads-skipper-beta

We had to implement several if-def sections and refact some import/export but based on our unit testing everything is working smoothly.

Answered: Php 8 attributes errors

Wed, 17 Aug 2022 16:30:38 +0000

Hello Steeve,

we just released new Skipper version with several bug fixes including fixes to issues you reported (wrong options, wrong discriminator map, fix for missing new keyword, and a few other).

Version is automatically distributed as a new 3.3.1 version through our automatic updates or can be downloaded here:

https://www.skipper18.com/en/download

Please test it and let me know if you will find any other issues. Thanks

Answered: 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:20:40 +0000

Sorry for ultra-slow response but your question was marked as spam and we noticed it now.

This issue was already fixed in one of the latest versions.

Answered: Odd Maintenance Warning After Beta Load in May

Thu, 04 Aug 2022 07:23:45 +0000

Hello Stephen, sorry for the late reply.

I believe this issue is caused by the custom system theme.

What OS are you using and what theme, please?

Thanks

Answered: Doctrine Attributes dublicating skipper beta

Mon, 01 Aug 2022 20:40:19 +0000

Thanks again for the reporting and example project. This bug is now fixed in the latest beta here:

https://www.skipper18.com/support/402/downloads-skipper-beta

Please test it and let me know if you find anything else.

Thanks

Answered: Unique Constraint and Doctrine Table Name Error

Tue, 11 Jan 2022 07:22:11 +0000

Hello,

In case you need to export a different column name than the field name, you can use the "column name" property in ORM property editor.

You're experiencing this issue probably because @UniqueConstrains needs to have column list, not field liest. So you need to configure your Colum name properly.

Answered: Laravel Doc Block property types

Mon, 30 Aug 2021 08:51:13 +0000

The new beta is ready with fixes for these issues:

https://www.skipper18.com/support/402/downloads-skipper-beta

timestamp and timestamptz is exported as \Carbon\Carbon
uuid is exported as string
new property docPropertyType for type customization

Please test it and let me know.

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>

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

Thu, 14 Nov 2019 08:41:49 +0000

Hello Peter,

new version with a fix for this issue is ready. Please download it from our site or use the application auto update.

https://www.skipper18.com/en/download

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

Tue, 12 Nov 2019 09:57:18 +0000

Hi,

we're aware of this new restriction from Apple.

We already updated all our CI and have new binaries with positive notarized stamps.

Please download it from the beta section:

https://support.skipper18.com/402/downloads-skipper-beta

This beta also contains some GUI fixes caused by the latest OSX bugs

Edit: Currently we're working on auto-updater fixes and some more Catalina issues.

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

Thu, 07 Nov 2019 16:55:09 +0000

Fixed in latest beta

Answered: Starting a 2nd Skipper Instance raises a session restore question

Wed, 04 Sep 2019 08:36:05 +0000

Hello Radoslaw,

we're aware of this "glitch". This behavior is caused by the inner crash-restoration system. New instance found non-closed inner database so it displayed this dialog.

To fix this issue, it will be necessary to rework the inner system for application state for multiple processes. But such rework can introduce a lot of new bugs and ambiguous states (ie. how to decide which of several states are active instances and which are crashed, how to restore app when multiple states are found, etc.).

Because of that, we decided to keep things simple. Because Skipper allows to open multiple projects in one instance this should not be a big deal.

On the other side, we don't want to restrict application to single-instance only because there is no real reason for this except this dialog ;-).

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

Fri, 19 Jul 2019 06:51:35 +0000

Thank you for suggestion and sorry for the inconvenience. You're right that would be great to implement such a feature.

Unfortunately, on all other OS, we're still supporting all previous versions including Windows XP, but Apple continuously forcing us to upgrade our build machines and eliminate support of old versions of OSX.

Although we would love to support old versions, there were some critical fixes (security and stability) which were released only for the newest XCode environment. Unfortunately, this meant to cut old OSX versions.

Anyway, previous versions can be found here: https://www.skipper18.com/en/download/previous-releases

Answered: Skipper Changes Non-Entity Variables Annotations

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

Thanks for the report. This is probably caused by something unusual/invalid in the file. Some uncommon formatting, invalid escape characters, etc.

To be able to fix it, I would need this complete Php file together with Skipper file with this entity.

It's sufficient to erase all other entities from Skipper project as same as erasing all inner logic from the Php file as long as this error still occurs.

If possible, send such project and php file to my email ludek.vodicka@skipper18.com

Thanks

Answered: Index field names not generated as column names

Thu, 21 Sep 2017 15:50:28 +0000

Thanks for info. We will check it.

Answered: wrong extension in doctrine2 xml export

Fri, 07 Jul 2017 07:43:54 +0000

You probably have configured file name for each entity with yml extension (this is a way how Skipper imports existing projects).

In this situation you need to change/remove file name to respect correct file name (Entity->Orm propety editor-> file name)

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

Fri, 19 May 2017 18:32:31 +0000

Hi Dave,

as mentioned in previous answers, there are serious problems with YAML Gedmo definitions. There are two (maybe three) kind of formats which Gedmo YML is using. And when we fixed the first one, we broke the second one.

The first one is using referred "- anything" format and the second one "anything" format.

And unfortunately, it isn't possible to maintain such inconsistent form. So yes, you're right that versions before 3.2.10 exported correctly mentioned situation (soft* vs -soft*) but incorrectly exported another half of use cases. And when we fixed the second half, we broke the first one.

Because of such inconsistency together with official statements that Yml will not be supported in future Doctrine versions (for example here) we decided to surrender our attempts and left yml format in current state.

The best way what can our users do is to re-export all definitions to the different format. Because you (and a lot of other users) are using Skipper to export Doctrine2 definitions, there is no reason to export it to inconsistent YML instead of fully supported and explicit XML.

It's a matter of few clicks to change the format from YML to XML. After that, you will get fully functional export and complete Gedmo support.

Although we loved to support all formats (including the forbidden ones) we're not able to support such inconsistent format which using several forms to describe the same thing.

Thanks for understanding.

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

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

Thanks for info. This is probably a bug. We will check it

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

Fri, 07 Apr 2017 07:06:31 +0000

Thanks for info. Did you send the crash report? Screenshot of the window is unfortunately useless to find the issue.

And can you please create screencast video with exact steps how to reproduce it? It would help us a lot.

Thanks

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;

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

Thu, 01 Oct 2015 17:19:41 +0000

Thanks for message.

It seems that there is an inconsistency in Doctrine2 specification because in XML this is a valid specification:

<entity name="User">
    <embedded name="address" class="Address" use-column-prefix="false" />
</entity>

but in annotation this is a correct form:

  /** @Embedded(class = "Address", columnPrefix = false) */

We have to find a way how to allow to define single property for two different names. In the meanwhile feel free to manually update Doctrine2.cfg.xml file located in installation directory and update "use-column-prefix" definition to "column-prefix".

Ludek