William Owusu (born 1991)

William Hazao Owusu (born 13 September 1991) is a Ghanaian footballer who plays for Turkish Cypriot club Gençlik Gücü.

William Hazao
Personal information
Full name William Hazao Owusu
Date of birth (1991-09-13) 13 September 1991
Place of birth Ghana
Height 1.82 m (5 ft 11 12 in)
Playing position(s) Midfielder
Club information
Current team
Gençlik Gücü
Number 18
Youth career
Sekondi Wise Fighters
Senior career*
Years Team Apps (Gls)
2009–2010 Sekondi Wise Fighters ? (?)
2010–2011 Hapoel Tel Aviv 0 (0)
2011Sektzia Nes Tziona (loan) 14 (0)
2011–2013 F.C. Ashdod 0 (0)
2011–2013Hapoel Kfar Saba (loan) 15 (18)
2013–2014 Beitar Tel Aviv Ramla 24 (5)
2014–2016 Hapoel Nazareth Illit 28 (5)
2017– Gençlik Gücü 1 (1)
* Senior club appearances and goals counted for the domestic league only and correct as of 13 September 2010

Career

William played for Sekondi Wise Fighters in the 2009/10 season Ghana Premier League season, finishing 15th in the 2009/10 Ghana Premier League season. Eli Guttman, then Hapoel Tel Aviv's Manager, enthusiastic young talents called him and asked to purchase long-term investment.[1] After F.C. Ashdod wanted him, and they signed William as a Hapoel player to help the talented team in the league as a temporary player replacement, but after the team was unable to sign their fifth 1st choice foreign player, it was decided William will be the fifth foreign player.[2] On January 2011, William went on loan to Sektzia Nes Tziona F.C., playing in the second division of Israeli football.

gollark: > sqlite is not less complex than this formatYes. *But*, you don't actually have to interact with the SQLite disk format directly because libsqlite3 exists.
gollark: I suspect SQLite would lose out somewhat in storage efficiency, but it could plausibly be faster for many things at runtime.
gollark: It's less complex for everyone interacting with it, since they can just... use SQLite, which has bindings for everything, instead of "zimlib". And by "efficiency" do you mean "space efficiency" or "lookup efficiency"? Because, as I said, SQLite would probably only add a few bytes per directory entry row, which is not a significant increase.
gollark: SQLite's overhead is pretty low, and the majority of the filesize is from the binary blobs which would remain the same in each.
gollark: It's less complex for them as the code is already there and written with a nice API, and "less efficient" how? Slightly more space on headers?

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.