Mobiles with gomobile

This is great. Anyone know if this runs embedded on mobile ?
Will be much easier to manage that sqlite !

[smola]

@gedw99 Note that go-mysql-server does not compete with sqlite. Both by design and by current project status.

The main design difference is that go-mysql-server is not a full-blown database. It is a storage-independent engine. go-mysql-server does not provide a storage backend (other than an in-memory one that we use for testing). If you want to read persisted data, you need to provide your own storage implementation. The storage backend could be CSV or sqlite itself.

On the current status of the project:

1. We do not support as many SQL features as sqlite.
2. INSERT/UPDATE queries are quite limited, we are focused on SELECT queries.
3. Our performance probably doesn't even come close to sqlite.

That being said, we'll appreciate help from the community on getting it to work with gomobile. It is something we don't plan to do ourselves in the short term though.

thanks for the thought rundown on the scope. I can have a go at go at getting it working. first i need to work out though how to have a backing store. I am guessing that FK are not supported for updates and so the data is really held as denormalised data ? Once i know this is makes it much easier to see what backing store would be appropropriate

…

On Mon, 21 May 2018 at 14:57 Santiago M. Mola ***@***.***> wrote: @gedw99 <https://github.com/gedw99> Note that go-mysql-server does not compete with sqlite. Both by design and by current project status. The main design difference is that go-mysql-server is not a full-blown database. It is a storage-independent engine. *go-mysql-server does not provide a storage backend* (other than an in-memory one that we use for testing). If you want to read persisted data, you need to provide your own storage implementation. The storage backend could be CSV or sqlite itself. On the current status of the project: 1. We do not support as many SQL features as sqlite. 2. INSERT/UPDATE queries are quite limited, we are focused on SELECT queries. 3. Our performance probably doesn't even come close to sqlite. That being said, we'll appreciate help from the community on getting it to work with gomobile. It is something we don't plan to do ourselves in the short term though. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#198 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATuCwiMN-n7G6UPEHzUCgAROa7Lu38Gbks5t0rnMgaJpZM4UGL-S> .

[smola]

@gedw99 Right. Primary keys, foreign keys or any other constraint are not supported yet. UPDATE is not supported yet either, only INSERT.

In our primary use case (i.e. gitbase) we never write data, only read data that already exists in the backend. So INSERT has just been used for convenience during testing with the in-memory backend.

In the mem package you have an in-memory backend that you can use for testing, or to check how to implement a new one.

@smola thanks - its clear. Its weird though. Why not just use a KV store then since thats all your needing. Its not trolling... just curious. I guess the answer is that you want to make it a sql store and started with what you needed for now.

[smola]

@gedw99 Our goal is providing a SQL interface that people is familiar with. It's not just "KV" stuff, but joins, group by, order by, subqueries, expressions, etc. The project is intentionally not implementing storage in the core, and probably never will, since we are not trying to build a database, just a SQL interface for arbitrary storage backends.

ok got it ! makes it clear what the intent is. thanks. This is quite cool.

…

On Wed, 23 May 2018 at 12:48 Santiago M. Mola ***@***.***> wrote: @gedw99 <https://github.com/gedw99> Our goal is providing a SQL interface that people is familiar with. It's not just "KV" stuff, but joins, group by, order by, subqueries, expressions, etc. The project is intentionally not implementing storage in the core, and probably never will, since we are not trying to build a database, just a SQL interface for arbitrary storage backends. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#198 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATuCwkkJbuCMJcf_EqBdj5QfK1_6VYaeks5t1T5_gaJpZM4UGL-S> .

[ajnavarro]

Closing this as resolved. @gedw99 if you have any other question, don't hesitate to do it.