<Qboid>
VITAS: Thomas left a message for you in #spacedock [16.04.2017 21:12:32]: "When you have time, could you export the db from prod, mask all the sensitive data, and upload that for me? Need test data for the migration script (and not guessing the schema would be cool too :D)"
<VITAS>
also what do we consider sensetive? :/
<VITAS>
wouldnt it be a good idea to write a random testdata gen? :)
<Thomas>
VITAS: Passwords and emails?
<Thomas>
UPDATE users SET password='test';
<Thomas>
UPDATE users SET email='test';
<Thomas>
Done :P
<VITAS>
do they need to be replaced by useable data?
<Thomas>
No
<VITAS>
not done because dublicate email
<Thomas>
I dont check if the data is useable in the script
<VITAS>
#i was aiming at some way to generate data localy if you want to contribute
<VITAS>
but i can do the email foo but it will take some foreach
<Thomas>
I think that would be easier
<Thomas>
VITAS: Hmm, I found a masked db on dev
<Thomas>
with all emails changed to censored@censored.sd
<VITAS>
unique!
<Thomas>
But why? Its for testing
<VITAS>
the column is uinque
<VITAS>
so either change that or have individual email adrs
<VITAS>
thats why i said foreach
<Thomas>
In this db dump the field isnt unique
<Thomas>
And in SDB it isn't unique too
<VITAS>
tht shouldnt be
<Thomas>
Well, unique-ness is managed by SDB, not the db
<VITAS>
should be both
<VITAS>
always
<Thomas>
Yeah, I can change it
<VITAS>
ok i hope my editor doesnt crash
<VITAS>
will take a while
<Thomas>
Thanks
<SpaceDock>
[SpaceDock-Backend] StollD pushed 2 new commits to go: https://git.io/vSd0B
<SpaceDock>
SpaceDock-Backend/go 415f843 Dorian Stoll: Looked at dev instead of master >.<
<SpaceDock>
SpaceDock-Backend/go 50cdfd6 Dorian Stoll: Make emails unique
<SpaceDock>
[SpaceDock-Backend] StollD pushed 3 new commits to go: https://git.io/vSdEN
<VITAS>
how do you save twitter usernames and such?
<VITAS>
as json datatype or as seperate table?
<VITAS>
also if you want something interresting to play with: take a look at orientdb (graph db)
<Thomas>
VITAS: In the meta field
<Thomas>
meta is a string, and I store json in it
<Thomas>
at runtime I decode that into an actual object
<VITAS>
hmm check if json is faster than having a key val table with uid link
<VITAS>
my gues is it still is faster but just to be sure
<VITAS>
there also need to be a salt in the table?
<Thomas>
I dont want to use seperate tables for every objects, because then I would need seperate objects in go too. And I would have a seperate meta table for every *normal* table
<Thomas>
I could use something like BSON to reduce the size though
<VITAS>
my concern is about db load
<Thomas>
Umm, there is no salt in the table, and there never was one
<VITAS>
i think json in rows is still faster than nested selects
<VITAS>
and there should be in the future
<Thomas>
With a seperate tables you need two queries, json is integrated into the query the backend does anyway
<Thomas>
-a
<VITAS>
you could fill in the salt as users login (rehash with salt)
<VITAS>
or just double hash
<VITAS>
yes btw json datatype and postgressql. is that a thing?
<Thomas>
postgres supports it iirc, but nether the database driver in go nor the orm does
<VITAS>
k
<VITAS>
not important just wanted to know
<VITAS>
mariadb is the one thats important
<SpaceDock>
[SpaceDock-Backend] StollD pushed 1 new commit to go: https://git.io/vSdx0
<SpaceDock>
SpaceDock-Backend/go efa52ac Dorian Stoll: mod_followers isn't autocreated, do that manually
<SpaceDock>
[SpaceDock-Backend] StollD pushed 1 new commit to go: https://git.io/vSdxz
<SpaceDock>
[SpaceDock-Backend] StollD commented on issue #23: Even though nobody has said something about this, I am going to merge it.... https://git.io/vSFIO