|
Title: Developing a blockchain SQL database named CovenantSQL Post by: CovenantSQL on September 13, 2018, 12:16:29 PM Guys, I'm developing a blockchain SQL database named CovenantSQL.
Our website: http://covenantsql.io GitHub: https://github.com/CovenantSQL/CovenantSQL so, any question? Title: Re: Developing a blockchain SQL database named CovenantSQL Post by: Patatas on September 13, 2018, 12:58:30 PM Guys, I'm developing a blockchain SQL database named CovenantSQL. Beautiful! Which is the core language of the entire project? By putting it on blockchain, do you remove the central authority completely? I know BigChainDb does it to a certain extent by your architecture seems more complicated. Would a developer have to learn an additional language to use this or the syntax remains the same as conventional SQL?https://github.com/CovenantSQL/CovenantSQL so, any question? Title: Re: Developing a blockchain SQL database named CovenantSQL Post by: Barcoded on September 13, 2018, 12:58:38 PM Can u please tell what use cases fits best for this database?
Title: Re: Developing a blockchain SQL database named CovenantSQL Post by: Patatas on September 13, 2018, 01:09:18 PM Can u please tell what use cases fits best for this database? A lot of them depending on the problem you're trying to solve...Some of them could be - A public data-base where data can't be altered (immutability) - Some records which store history like medical records which can only be updated by not overwritten. On the technical end, it's decentralised and hence there is no central authority over the database. Title: Re: Developing a blockchain SQL database named CovenantSQL Post by: Barcoded on September 13, 2018, 01:32:20 PM Can u please tell what use cases fits best for this database? A lot of them depending on the problem you're trying to solve...Some of them could be - A public data-base where data can't be altered (immutability) - Some records which store history like medical records which can only be updated by not overwritten. On the technical end, it's decentralised and hence there is no central authority over the database. So, this database allows only INSERT and SELECT WHERE id=? and UPDATE ... WHERE id=? or it also allows more complex queries? Title: Re: Developing a blockchain SQL database named CovenantSQL Post by: CovenantSQL on September 14, 2018, 08:44:20 AM Guys, I'm developing a blockchain SQL database named CovenantSQL. Beautiful! Which is the core language of the entire project? By putting it on blockchain, do you remove the central authority completely? I know BigChainDb does it to a certain extent by your architecture seems more complicated. Would a developer have to learn an additional language to use this or the syntax remains the same as conventional SQL?https://github.com/CovenantSQL/CovenantSQL so, any question? We developing it in golang and c. Sure, it's completely decentralized, so we have wrote 50k lines of golang to implement it. currently, we have java and golang driver, the usage is just same like a traditional database. the test net will be on by Oct. 2018 Title: Re: Developing a blockchain SQL database named CovenantSQL Post by: CovenantSQL on September 14, 2018, 08:57:31 AM Can u please tell what use cases fits best for this database? A lot of them depending on the problem you're trying to solve...Some of them could be - A public data-base where data can't be altered (immutability) - Some records which store history like medical records which can only be updated by not overwritten. On the technical end, it's decentralised and hence there is no central authority over the database. thx for explaining, some more 1. For traditional App using SQL, you can adapt it onto Blockchain by little change on DB-type and DB-uri. 2. For ĐApp it can be a large and cheap(comparing to storage on Bitcoin or Ethereum) rational database. Title: Re: Developing a blockchain SQL database named CovenantSQL Post by: CovenantSQL on September 14, 2018, 09:11:39 AM Can u please tell what use cases fits best for this database? A lot of them depending on the problem you're trying to solve...Some of them could be - A public data-base where data can't be altered (immutability) - Some records which store history like medical records which can only be updated by not overwritten. On the technical end, it's decentralised and hence there is no central authority over the database. So, this database allows only INSERT and SELECT WHERE id=? and UPDATE ... WHERE id=? or it also allows more complex queries? most SQL-92 standard is supported. that is you can even write SQL like this: Code: SELECT urls.url |