You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the latest version of node-appwrite (11.1.0) and have set up some scripts to set up my projects programmatically. Everything works fine besides creating array attributes, when I try this code:
message: 'Cannot set default value for array attributes',
code: 400,
type: 'attribute_default_unsupported',
version: '1.4.13'
And when I try to use any other value instead of empty string for a 'default value' parameter, SDK throws another error saying that only string with size 0 can be used as a parameter.
馃憤 Expected behavior
Attribute is created.
馃憥 Actual Behavior
Exception thrown.
馃幉 Appwrite version
Version 0.10.x
馃捇 Operating system
Linux
馃П Your Environment
No response
馃憖 Have you spent some time to check if this issue has been raised before?
@algusarov, thanks for creating this issue! 馃檹馃徏 This is expected. The goal for setting a default is to not have nulls. This isn't a problem with arrays because they will never be null.
That said, you are more than welcome to add your thoughts to appwrite/console#461 and add a 馃憤馃徏
馃憻 Reproduction steps
I'm using the latest version of node-appwrite (11.1.0) and have set up some scripts to set up my projects programmatically. Everything works fine besides creating array attributes, when I try this code:
await db.createStringAttribute(databaseId, collectionId, 'media', 10000, false, '', true)
it generates this exception:
Cannot set default value for array attributes
And when I try to use any other value instead of empty string for a 'default value' parameter, SDK throws another error saying that only string with size 0 can be used as a parameter.
馃憤 Expected behavior
Attribute is created.
馃憥 Actual Behavior
Exception thrown.
馃幉 Appwrite version
Version 0.10.x
馃捇 Operating system
Linux
馃П Your Environment
No response
馃憖 Have you spent some time to check if this issue has been raised before?
馃彚 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: