> The only way I can think of to achieve this is to create a separate schema > and use triggers that > selectively copy only the records you want into this new schema and replicate > only this new schema. You
> will have to use binlog_format=ROW. Peharps the request just meant ROW format. Then not to transfer only updated fields of a record one also needs --binlog-row-image=MINIMAL. > > On Thu, 13 Jul 2023, 04:25 Andrew Gable via discuss, > <[email protected]> wrote: > > Hi Everyone, > > I hope someone can guide me. > > here is my issue > > I have a central database that is running in my back office and each of > my front end machines have a > database that is used just for the front end. > > most of the data that is stored in the back office is not needed on the > front end but the product table > is. > > the product table hold more information then what is needed on the front > end (the front end system does > not need to know who the supplier is of the item for example) > > so I have the following feilds on the front end database (called > posdatabase) > barcodenumber > posdeacription > pricetype > salelocation > Systemprice. > > both database are using the same field names > > is it possible to use replication on select Feilds on the master to the > slave? I have seen on YouTube > lots of videos showing replication of every table and field in a database > but I don't need that) > > what I want to do is that possible? I wonder whether your use case might actually be something like COLUMN replication. That is when a master M table record M: <A INT, B INT, C INT> is updated subsets of its columns are replicated to different slave servers. E.g S1,S2,S3 that subcribed to a single column could receive it as S1: <A> S2: <B> S3: <C> _______________________________________________ discuss mailing list -- [email protected] To unsubscribe send an email to [email protected]
