Public Roadmap ?

[carlospaulino]

I am trying to figure out ways to contribute to this project, but from what I see there is no public roadmap. Do you have one available that you can add to the wiki? If not, could we start a conversation around potential features? For example:

• Support for coroutines.
• Paranoid mode. (mark row as deleted instead of deleting)
• Auto createdAt/updatedAt.
• Improved documentation.
• Schema migrations.
• Etc.

[raderio]

Paranoid mode. (mark row as deleted instead of deleting)

What do you mean by this?

[carlospaulino]

@raderio it means that we don't delete database entries but set a date field(deletedAt) to the current date.

[raderio]

@carlospaulino can you please be more detailed what are use cases?

[Tapac]

@carlospaulino sorry for the late answer.

It's nice to hear that you wish to contribute to the project.
As you can see from github issues - there are many places for improvements, but as Exposed is just a side project for me it's not always possible to fix most of them.

I'll try to create an roadmap.md or maybe a page on wiki, but at the moment the plan is:

1. Replace joda-time as date-time library with plugable approach which will allow to chose among joda/java8 time/theeten and also fix all the issues tagged with datetime. It's partially made in date-split-modules branch.
2. Next step is to split Exposed to modules as core, dao + per-database modules.
3. Refactor test to cover different jdbc-drivers/database versions (with docker-compose or test containers)
4. Support coroutines and eliminate thread-local based transaction manager
5. Make attempt to move from jdbc to something more asynchronous.

[hanggrian]

@Tapac in no. 2 scenario, would it be then possible to add support for NoSQL in separate module?

[Tapac]

@hendraanggrian , I'm not sure that Exposed DSL suites well NoSQL approach, but you can try https://github.com/cheptsov/kotlin-nosql