# DDL just for Percona

**URL:** <https://forums.percona.com/t/ddl-just-for-percona/39512>\
**Category:** Percona Distribution for MySQL\
**Created:** [October 8, 2025, 11:59am UTC](https://forums.percona.com/t/ddl-just-for-percona/39512 "2025-10-08T11:59:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Phillip85](https://avatars.discourse-cdn.com/v4/letter/p/9d8465/32.png) [@Phillip85](https://forums.percona.com/u/Phillip85)\
**Post date:** [October 8, 2025, 11:59am UTC](https://forums.percona.com/t/ddl-just-for-percona/39512/1 "2025-10-08T11:59:42Z")

</div>

Hi,  
is it possible to Comment a Part of a DDL to just get used on percona server?

I want to use the Percona exclusive compressed column in a Projekt which needs to be compatible to mysql / mariadb too.

When i try it like this

```auto
create table `test`
(
    `id` bigint unsigned not null auto_increment 
    `file` LONGBLOB /*!50633 COLUMN_FORMAT COMPRESSED */ null,
    `created_at` timestamp null,
    `updated_at` timestamp null
) default character set utf8mb4
  collate 'utf8mb4_unicode_ci'

```

the create table works on percona, but a mysql or a mariadb server creates a

`Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'COMPRESSED */ null,`

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [October 8, 2025, 4:18pm UTC](https://forums.percona.com/t/ddl-just-for-percona/39512/2 "2025-10-08T16:18:03Z")

</div>

Hello @Phillip85,  
Unfortunately no. SQL comments, and more specifically, versioned comments, are not filterable by db flavor (ie: percona, community, maria).

> [@Phillip85](#):
>
> I want to use the Percona exclusive compressed column in a Projekt which needs to be compatible to mysql / mariadb too

This is confusing. If you want to use a Percona feature, why are you messing with community/maria? That doesn’t make sense to me. Pick 1 database flavor, and use it. Mariadb is not considered mysql anymore; treat it as a different database.

---

<div class="post-metadata">

**Author:** ![Phillip85](https://avatars.discourse-cdn.com/v4/letter/p/9d8465/32.png) [@Phillip85](https://forums.percona.com/u/Phillip85)\
**Post date:** [October 9, 2025, 12:31pm UTC](https://forums.percona.com/t/ddl-just-for-percona/39512/3 "2025-10-09T12:31:39Z")

</div>

Hello @matthewb ,  
the project is used by different users with different db flavors.  
Till now, the requirement was just mysql or a drop in replacement.  
So I have to think about changing the requirements.

Thanks for the answer  
Phillip

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [October 9, 2025, 3:44pm UTC](https://forums.percona.com/t/ddl-just-for-percona/39512/4 "2025-10-09T15:44:48Z")

</div>

Percona MySQL is a drop-in replacement for Community MySQL, offering enhanced performance, and better features (as you experienced). We maintain 100% compatibility with upstream. MariaDB is not mysql.

My analogy:  
MySQL Community: Scoop of vanilla ice cream  
Percona MySQL: same scoop, but add whip cream, hot fudge sauce, sprinkles (same base, just better)  
MariaDB: Yogurt