Migrating Database Collections from dart about dart-sdk HOT 10 CLOSED

On Tue, 31 Jan 2023 at 3:56 PM Gani Georgiev ***@***.***> wrote: Closed #28 <#28> as completed. — Reply to this email directly, view it on GitHub <#28 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIUFLXAU4EM4TEBPI7GUSU3WVDZHVANCNFSM6AAAAAAUMH25ZI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

On Wed, 1 Feb 2023 at 12:25 AM Popal ***@***.***> wrote: Can you show us an example of adding a new column to a collection or removing a column from a collection On Tue, 31 Jan 2023 at 3:56 PM Gani Georgiev ***@***.***> wrote: > Closed #28 <#28> as > completed. > > — > Reply to this email directly, view it on GitHub > <#28 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AIUFLXAU4EM4TEBPI7GUSU3WVDZHVANCNFSM6AAAAAAUMH25ZI> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

On Wed, 1 Feb 2023 at 12:27 AM Popal ***@***.***> wrote: About auto migration Can you please show us an example of how updating or adding of a column work there And How we can put migrating files in our repo and start a new project with the same tables On Wed, 1 Feb 2023 at 12:25 AM Popal ***@***.***> wrote: > Can you show us an example of adding a new column to a collection or > removing a column from a collection > > On Tue, 31 Jan 2023 at 3:56 PM Gani Georgiev ***@***.***> > wrote: > >> Closed #28 <#28> as >> completed. >> >> — >> Reply to this email directly, view it on GitHub >> <#28 (comment)>, or >> unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AIUFLXAU4EM4TEBPI7GUSU3WVDZHVANCNFSM6AAAAAAUMH25ZI> >> . >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >> >

On Wed, 1 Feb 2023 at 1:04 AM Gani Georgiev ***@***.***> wrote: Can you show us an example of adding a new column to a collection or removing a column from a collection Here is an example using the Dart SDK (*I haven't tested it, but it should give you an idea of the expected workflow*): final pb = PocketBase("http://127.0.0.1:8090"); final collection = await pb.collections.getOne("uktsrgciaq83ltm"); // add a new collection field... collection.schema.add(SchemaField( id: "someRandomFieldId", // optional (it will be auto generated if missing) name: "myNewField", type: "text", required: true, // options differ depending on the field type // all field types and their options could be found in // ***@***.***/models/schema // (the `json` value is the body key, for example the date options are ***@***.***/models/schema#DateOptions) options: <String, dynamic>{ "min": 10, }, )); // remove a field (aka. remove an element from the List) collection.schema.removeAt(2); // rename a field (aka. edit an existing List element) collection.schema[1].unique = false; // persist changesawait pb.collections.update(collection.id, body: collection.toJson()); ------------------------------ About auto migration. Can you please show us an example of how updating or adding of a column work there. How we can put migrating files in our repo and start a new project with the same tables The automigrations are automanaged, aka. when doing collection changes from the Admin UI or via the web API (as in the previous SDK example), it will automatically generate a js migration file for you in the pb_migrations folder. You can copy this folder to another location and place it next to your pb_data (*or if you want to specify a specific location, you can also use the --migrationsDir="/path/to/pb_migrations" flag when starting PocketBase; more info you can find with the --help flag* ). ------------------------------ When we ship a new version of our application adding columns or renaming column shall be done automatically I'm not sure what to recommend. As mentioned, for now offline/local-first data handling is not supported out of the box and this require some manual management from the developer side. I don't think there is a single generic solution for this since it really depends on your use case and the desired deployment flow, eg. how you are connecting to the remote server, how you are planning to propagate and sync changes, how you are planning to handle schema conflicts (eg. the user locally created a column with the same name but different id as your new remote update), etc. — Reply to this email directly, view it on GitHub <#28 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIUFLXGQ4SHDHCKXH66BGTDWVFZMDANCNFSM6AAAAAAUMH25ZI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

On Wed, 1 Feb 2023 at 10:41 AM Popal ***@***.***> wrote: Thank you so much for your guidance Great seeing that there is a way to add, remove or rename a column and change its property The automigration is a new way of migrating database and I think it will solve our problem As we want to automigrate our database with each new version of our flutter app we ship. About how we backup: we take user pb_data folder and save it in our server. About sync: we need a sync feature but still don’t know how we can implement it, this is a missing feature with package: drift we used so far. Thank you for your response and great replay. On Wed, 1 Feb 2023 at 1:04 AM Gani Georgiev ***@***.***> wrote: > Can you show us an example of adding a new column to a collection or > removing a column from a collection > > Here is an example using the Dart SDK (*I haven't tested it, but it > should give you an idea of the expected workflow*): > > final pb = PocketBase("http://127.0.0.1:8090"); > final collection = await pb.collections.getOne("uktsrgciaq83ltm"); > // add a new collection field... > collection.schema.add(SchemaField( > id: "someRandomFieldId", // optional (it will be auto generated if missing) > name: "myNewField", > type: "text", > required: true, > // options differ depending on the field type > // all field types and their options could be found in > // ***@***.***/models/schema > // (the `json` value is the body key, for example the date options are ***@***.***/models/schema#DateOptions) > options: <String, dynamic>{ > "min": 10, > }, > )); > // remove a field (aka. remove an element from the List) > collection.schema.removeAt(2); > // rename a field (aka. edit an existing List element) > collection.schema[1].unique = false; > // persist changesawait pb.collections.update(collection.id, body: collection.toJson()); > > ------------------------------ > > About auto migration. Can you please show us an example of how updating > or adding of a column work there. > How we can put migrating files in our repo and start a new project with > the > same tables > > The automigrations are automanaged, aka. when doing collection changes > from the Admin UI or via the web API (as in the previous SDK example), it > will automatically generate a js migration file for you in the > pb_migrations folder. You can copy this folder to another location and > place it next to your pb_data (*or if you want to specify a specific > location, you can also use the --migrationsDir="/path/to/pb_migrations" > flag when starting PocketBase; more info you can find with the --help flag* > ). > ------------------------------ > > When we ship a new version of our application adding columns or renaming > column shall be done automatically > > I'm not sure what to recommend. As mentioned, for now offline/local-first > data handling is not supported out of the box and this require some manual > management from the developer side. I don't think there is a single generic > solution for this since it really depends on your use case and the desired > deployment flow, eg. how you are connecting to the remote server, how you > are planning to propagate and sync changes, how you are planning to handle > schema conflicts (eg. the user locally created a column with the same name > but different id as your new remote update), etc. > > — > Reply to this email directly, view it on GitHub > <#28 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AIUFLXGQ4SHDHCKXH66BGTDWVFZMDANCNFSM6AAAAAAUMH25ZI> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >