Skip to content
This repository was archived by the owner on Apr 14, 2022. It is now read-only.

Support 1:N connection using array field with IDs #102

Closed
Totktonada opened this issue Mar 29, 2018 · 3 comments
Closed

Support 1:N connection using array field with IDs #102

Totktonada opened this issue Mar 29, 2018 · 3 comments
Labels
archived enhancement New feature or request wontfix This will not be worked on

Comments

@Totktonada
Copy link
Member

It is useful for known to be small amount of child items.

@Totktonada Totktonada added the enhancement New feature or request label Mar 29, 2018
@SudoBobo SudoBobo self-assigned this Apr 2, 2018
Totktonada added a commit that referenced this issue Sep 4, 2018
* fix format_process function
* print whole reject file when test failed (#102)
* print reproduce file when test failed at -j -1 mode (#104)
* print reproduce file content in parallel mode (#104)
* allow to pass arguments to create_cluster
* allow grep_log to not reset search results after tarantool restart
* support comments in config files
* don't kill default if non-default crash expected (#109)
* don't inherit unneeded file descriptors (#117)
* list task for hung workers (#107)
* add new config param 'show_reproduce_content' (#113)
Totktonada added a commit that referenced this issue Sep 4, 2018
* fix format_process function
* print whole reject file when test failed (#102)
* print reproduce file when test failed at -j -1 mode (#104)
* print reproduce file content in parallel mode (#104)
* allow to pass arguments to create_cluster
* allow grep_log to not reset search results after tarantool restart
* support comments in config files
* don't kill default if non-default crash expected (#109)
* don't inherit unneeded file descriptors (#117)
* list task for hung workers (#107)
* add new config param 'show_reproduce_content' (#113)
@RunsFor
Copy link

RunsFor commented Jan 30, 2019

It would be also useful to be able to use associative array keys as IDs in connection

@Totktonada
Copy link
Member Author

@RunsFor Can you please clarify it in a bit more formal way? Some example or kinda.

@Totktonada Totktonada added wontfix This will not be worked on archived labels Apr 13, 2022
@Totktonada
Copy link
Member Author

I'm going to archive the repository. I'll proceed as follows:

  • Mark all open pull requests with the archived label and close.
  • Mark all open issues with archived and wontfix labels and close.
  • Archive the repository.

Consider the following projects:

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
archived enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants