On 10/08/2019 09:48, mhysnm1...@gmail.com wrote:
> HI all,
>
> I have multiple different accounts that I am creating reports for. Thus I
> cannot have a centralised transaction table that contains all the records.
> These different accounts are for different organisations or for other
> members in
On 8/9/2019 7:39 AM, Alan Gauld via Tutor wrote:
On 09/08/2019 09:54, mhysnm1...@gmail.com wrote:
updates and insertions. I have multiple tables with the same structure with
differe
I agree 100% with Peter and Alan's responses.
--
Bob Gailer
___
Tu
On 09/08/2019 09:54, mhysnm1...@gmail.com wrote:
> updates and insertions. I have multiple tables with the same structure with
> different names.
Umm, why?
Assuming by structure you mean they have the same fields
then that's usually a bad design decision.
Why not have one table with an attribute
mhysnm1...@gmail.com wrote:
> All,
>
>
>
> I think I am asking for the impossible here. But I will ask anyway.
>
>
>
> I am using flask_sqlalchemy to build the tables and perform the queries,
> updates and insertions. I have multiple tables with the same structure
> with diff
All,
I think I am asking for the impossible here. But I will ask anyway.
I am using flask_sqlalchemy to build the tables and perform the queries,
updates and insertions. I have multiple tables with the same structure with
different names. A table called accounts which stores t
