Skip to content

Introduce data objects for Table / Column #19

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

Introduce data objects for Table / Column #19

wants to merge 2 commits into from

Conversation

bjoernhaeuser
Copy link
Collaborator

Hey,

I am currently trying to serialize the table_map to a file. The thing is the table_map consists of TableMapEvents, which makes it rather hard to get a good serializable Object.

Therefore I thought that it would be nice to have a Table-Object, similiar to the Column-Object, which just holds the data. I also used a seperat dict (self.data) instead of self.__dict__, which again makes its easier to seriale and compare the objects based on the data.

What do you think?

Thanks in advance
Björn

The Table and Column objects are now there for just holding every data
in self.data. This makes its easier to serialize these objects.
@julien-duponchelle
Copy link
Owner

I just read the code and it sound good, i will test it tonight.

@julien-duponchelle
Copy link
Owner

Tested with Python 2.7 and 3 it's work

@julien-duponchelle
Copy link
Owner

Merged 58029d5

@julien-duponchelle
Copy link
Owner

I'm sorry but i have cherry pick your commit instead of merging the pull request.

You can see we have a commit already merged in the pull request:
capture_d_ecran_13_05_13_21_47

I think the best way to avoid this is to make pull request from a feature branch.

Thanks a lot for the precious contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants