Show current row “win streak” Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)Using Row_Number to find consecutive row countReset password for 'postgres' on v9.3 (Win Srv)Group by maximum consecutive rowMerging adjacent date intervals into a single rowTrigger function using current row and current table name as variablesTrigger function using current row and current table name as variables (final part)Selecting row grouped by an “add-on” indicatorFilter on time difference between current and next rowPostgreSQL: mark current session as “unimportant”How to count max date row if current status column is 0 or 2?

Does the Mueller report show a conspiracy between Russia and the Trump Campaign?

If Windows 7 doesn't support WSL, then what is "Subsystem for UNIX-based Applications"?

Positioning dot before text in math mode

What are the main differences between Stargate SG-1 cuts?

How can a team of shapeshifters communicate?

Does silver oxide react with hydrogen sulfide?

Delete free apps from library

Are the endpoints of the domain of a function counted as critical points?

How does light 'choose' between wave and particle behaviour?

What would you call this weird metallic apparatus that allows you to lift people?

How can I prevent/balance waiting and turtling as a response to cooldown mechanics

What initially awakened the Balrog?

Can two person see the same photon?

Google .dev domain strangely redirects to https

Is there public access to the Meteor Crater in Arizona?

What adaptations would allow standard fantasy dwarves to survive in the desert?

Why not send Voyager 3 and 4 following up the paths taken by Voyager 1 and 2 to re-transmit signals of later as they fly away from Earth?

What does it mean that physics no longer uses mechanical models to describe phenomena?

Did Mueller's report provide an evidentiary basis for the claim of Russian govt election interference via social media?

Why datecode is SO IMPORTANT to chip manufacturers?

What is the difference between CTSS and ITS?

Trying to understand entropy as a novice in thermodynamics

One-one communication

Co-worker has annoying ringtone



Show current row “win streak”



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)Using Row_Number to find consecutive row countReset password for 'postgres' on v9.3 (Win Srv)Group by maximum consecutive rowMerging adjacent date intervals into a single rowTrigger function using current row and current table name as variablesTrigger function using current row and current table name as variables (final part)Selecting row grouped by an “add-on” indicatorFilter on time difference between current and next rowPostgreSQL: mark current session as “unimportant”How to count max date row if current status column is 0 or 2?



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








3















I need to show the running win/loss streak per row in a query, so given the table below, the query should return the "expected" column. I've tried some approaches with window functions, but no success.



create table matches (player text, dt date, is_winner boolean, expected integer )
insert into matches values
('A', '2019-01-01', TRUE, 0),
('A', '2019-01-03', TRUE, 1),
('A', '2019-01-04', TRUE, 2),
('A', '2019-01-09', FALSE, 0),
('A', '2019-01-10', FALSE, -1),
('A', '2019-01-15', TRUE, 0);


player dt is_winner expected
A 2019-01-01 true 0
A 2019-01-03 true 1
A 2019-01-04 true 2
A 2019-01-09 false 0
A 2019-01-10 false -1
A 2019-01-15 true 0



The logic is:



  1. Resets to 0 when winning after a loss, or losing after a win.

  2. Increments after a win, but not if it's case 1.

  3. Decrements after a loss, but not if it's case 1.

Any insights on how to tackle this are welcome. My last resort would be a function with a loop called by every row.










share|improve this question









New contributor




codigofontes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.


























    3















    I need to show the running win/loss streak per row in a query, so given the table below, the query should return the "expected" column. I've tried some approaches with window functions, but no success.



    create table matches (player text, dt date, is_winner boolean, expected integer )
    insert into matches values
    ('A', '2019-01-01', TRUE, 0),
    ('A', '2019-01-03', TRUE, 1),
    ('A', '2019-01-04', TRUE, 2),
    ('A', '2019-01-09', FALSE, 0),
    ('A', '2019-01-10', FALSE, -1),
    ('A', '2019-01-15', TRUE, 0);


    player dt is_winner expected
    A 2019-01-01 true 0
    A 2019-01-03 true 1
    A 2019-01-04 true 2
    A 2019-01-09 false 0
    A 2019-01-10 false -1
    A 2019-01-15 true 0



    The logic is:



    1. Resets to 0 when winning after a loss, or losing after a win.

    2. Increments after a win, but not if it's case 1.

    3. Decrements after a loss, but not if it's case 1.

    Any insights on how to tackle this are welcome. My last resort would be a function with a loop called by every row.










    share|improve this question









    New contributor




    codigofontes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.






















      3












      3








      3








      I need to show the running win/loss streak per row in a query, so given the table below, the query should return the "expected" column. I've tried some approaches with window functions, but no success.



      create table matches (player text, dt date, is_winner boolean, expected integer )
      insert into matches values
      ('A', '2019-01-01', TRUE, 0),
      ('A', '2019-01-03', TRUE, 1),
      ('A', '2019-01-04', TRUE, 2),
      ('A', '2019-01-09', FALSE, 0),
      ('A', '2019-01-10', FALSE, -1),
      ('A', '2019-01-15', TRUE, 0);


      player dt is_winner expected
      A 2019-01-01 true 0
      A 2019-01-03 true 1
      A 2019-01-04 true 2
      A 2019-01-09 false 0
      A 2019-01-10 false -1
      A 2019-01-15 true 0



      The logic is:



      1. Resets to 0 when winning after a loss, or losing after a win.

      2. Increments after a win, but not if it's case 1.

      3. Decrements after a loss, but not if it's case 1.

      Any insights on how to tackle this are welcome. My last resort would be a function with a loop called by every row.










      share|improve this question









      New contributor




      codigofontes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      I need to show the running win/loss streak per row in a query, so given the table below, the query should return the "expected" column. I've tried some approaches with window functions, but no success.



      create table matches (player text, dt date, is_winner boolean, expected integer )
      insert into matches values
      ('A', '2019-01-01', TRUE, 0),
      ('A', '2019-01-03', TRUE, 1),
      ('A', '2019-01-04', TRUE, 2),
      ('A', '2019-01-09', FALSE, 0),
      ('A', '2019-01-10', FALSE, -1),
      ('A', '2019-01-15', TRUE, 0);


      player dt is_winner expected
      A 2019-01-01 true 0
      A 2019-01-03 true 1
      A 2019-01-04 true 2
      A 2019-01-09 false 0
      A 2019-01-10 false -1
      A 2019-01-15 true 0



      The logic is:



      1. Resets to 0 when winning after a loss, or losing after a win.

      2. Increments after a win, but not if it's case 1.

      3. Decrements after a loss, but not if it's case 1.

      Any insights on how to tackle this are welcome. My last resort would be a function with a loop called by every row.







      postgresql gaps-and-islands






      share|improve this question









      New contributor




      codigofontes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question









      New contributor




      codigofontes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question








      edited 3 hours ago









      Paul White

      54.3k14288461




      54.3k14288461






      New contributor




      codigofontes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 10 hours ago









      codigofontescodigofontes

      183




      183




      New contributor




      codigofontes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      codigofontes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      codigofontes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.




















          1 Answer
          1






          active

          oldest

          votes


















          4














          I've done this in stages using CTEs so that you can see how it's done as the queries progress. Each CTE adds a column in the output in order to show you progress.



          It's pretty much self-documenting with the CTE names, to be honest.



          with lags as (
          select player,
          dt,
          is_winner,
          lag(is_winner) OVER (partition by player ORDER BY dt ASC) as prev_is_winner,
          expected
          from matches
          ),
          group_changes as (
          select lags.*,
          case
          when prev_is_winner <> is_winner or prev_is_winner is null
          then 1
          else 0
          end as is_new_group
          from lags
          ),
          groups_numbered as (
          select *,
          sum(is_new_group)
          over (partition by player order by dt, is_winner desc) as streak_group
          from group_changes
          ),
          expected_in_groups as (
          select groups_numbered.*,
          row_number()
          over (partition by player,streak_group
          order by dt asc, streak_group asc) - 1 as expected_unsigned
          from groups_numbered
          )
          select expected_in_groups.*, case when is_winner = 't' then expected_unsigned else expected_unsigned * -1 end as actual
          from expected_in_groups
          order by player asc, dt asc;


          DB Fiddle Link (I added an extra row just to make sure it was working at a certain point)



          Basically:




          1. lags CTE: use LAG() to get the previous result relative to the current row.


          2. group_changes CTE: Detect whether the previous streak, whether win or loss, has ended


          3. groups_numbered CTE: Give each streak a number


          4. expected_in_groups CTE: Number the rows in the group

          5. Final select: negate the loss streaks

          .



          +--------+------------+-----------+----------------+----------+--------------+--------------+-------------------+--------+
          | player | dt | is_winner | prev_is_winner | expected | is_new_group | streak_group | expected_unsigned | actual |
          +--------+------------+-----------+----------------+----------+--------------+--------------+-------------------+--------+
          | A | 2019-01-01 | t | | 0 | 1 | 1 | 0 | 0 |
          | A | 2019-01-03 | t | t | 1 | 0 | 1 | 1 | 1 |
          | A | 2019-01-04 | t | t | 2 | 0 | 1 | 2 | 2 |
          | A | 2019-01-09 | f | t | 0 | 1 | 2 | 0 | 0 |
          | A | 2019-01-10 | f | f | -1 | 0 | 2 | 1 | -1 |
          | A | 2019-01-11 | f | f | -2 | 0 | 2 | 2 | -2 |
          | A | 2019-01-15 | t | f | 0 | 1 | 3 | 0 | 0 |
          +--------+------------+-----------+----------------+----------+--------------+--------------+-------------------+--------+





          share|improve this answer

























            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "182"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );






            codigofontes is a new contributor. Be nice, and check out our Code of Conduct.









            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f235306%2fshow-current-row-win-streak%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            4














            I've done this in stages using CTEs so that you can see how it's done as the queries progress. Each CTE adds a column in the output in order to show you progress.



            It's pretty much self-documenting with the CTE names, to be honest.



            with lags as (
            select player,
            dt,
            is_winner,
            lag(is_winner) OVER (partition by player ORDER BY dt ASC) as prev_is_winner,
            expected
            from matches
            ),
            group_changes as (
            select lags.*,
            case
            when prev_is_winner <> is_winner or prev_is_winner is null
            then 1
            else 0
            end as is_new_group
            from lags
            ),
            groups_numbered as (
            select *,
            sum(is_new_group)
            over (partition by player order by dt, is_winner desc) as streak_group
            from group_changes
            ),
            expected_in_groups as (
            select groups_numbered.*,
            row_number()
            over (partition by player,streak_group
            order by dt asc, streak_group asc) - 1 as expected_unsigned
            from groups_numbered
            )
            select expected_in_groups.*, case when is_winner = 't' then expected_unsigned else expected_unsigned * -1 end as actual
            from expected_in_groups
            order by player asc, dt asc;


            DB Fiddle Link (I added an extra row just to make sure it was working at a certain point)



            Basically:




            1. lags CTE: use LAG() to get the previous result relative to the current row.


            2. group_changes CTE: Detect whether the previous streak, whether win or loss, has ended


            3. groups_numbered CTE: Give each streak a number


            4. expected_in_groups CTE: Number the rows in the group

            5. Final select: negate the loss streaks

            .



            +--------+------------+-----------+----------------+----------+--------------+--------------+-------------------+--------+
            | player | dt | is_winner | prev_is_winner | expected | is_new_group | streak_group | expected_unsigned | actual |
            +--------+------------+-----------+----------------+----------+--------------+--------------+-------------------+--------+
            | A | 2019-01-01 | t | | 0 | 1 | 1 | 0 | 0 |
            | A | 2019-01-03 | t | t | 1 | 0 | 1 | 1 | 1 |
            | A | 2019-01-04 | t | t | 2 | 0 | 1 | 2 | 2 |
            | A | 2019-01-09 | f | t | 0 | 1 | 2 | 0 | 0 |
            | A | 2019-01-10 | f | f | -1 | 0 | 2 | 1 | -1 |
            | A | 2019-01-11 | f | f | -2 | 0 | 2 | 2 | -2 |
            | A | 2019-01-15 | t | f | 0 | 1 | 3 | 0 | 0 |
            +--------+------------+-----------+----------------+----------+--------------+--------------+-------------------+--------+





            share|improve this answer





























              4














              I've done this in stages using CTEs so that you can see how it's done as the queries progress. Each CTE adds a column in the output in order to show you progress.



              It's pretty much self-documenting with the CTE names, to be honest.



              with lags as (
              select player,
              dt,
              is_winner,
              lag(is_winner) OVER (partition by player ORDER BY dt ASC) as prev_is_winner,
              expected
              from matches
              ),
              group_changes as (
              select lags.*,
              case
              when prev_is_winner <> is_winner or prev_is_winner is null
              then 1
              else 0
              end as is_new_group
              from lags
              ),
              groups_numbered as (
              select *,
              sum(is_new_group)
              over (partition by player order by dt, is_winner desc) as streak_group
              from group_changes
              ),
              expected_in_groups as (
              select groups_numbered.*,
              row_number()
              over (partition by player,streak_group
              order by dt asc, streak_group asc) - 1 as expected_unsigned
              from groups_numbered
              )
              select expected_in_groups.*, case when is_winner = 't' then expected_unsigned else expected_unsigned * -1 end as actual
              from expected_in_groups
              order by player asc, dt asc;


              DB Fiddle Link (I added an extra row just to make sure it was working at a certain point)



              Basically:




              1. lags CTE: use LAG() to get the previous result relative to the current row.


              2. group_changes CTE: Detect whether the previous streak, whether win or loss, has ended


              3. groups_numbered CTE: Give each streak a number


              4. expected_in_groups CTE: Number the rows in the group

              5. Final select: negate the loss streaks

              .



              +--------+------------+-----------+----------------+----------+--------------+--------------+-------------------+--------+
              | player | dt | is_winner | prev_is_winner | expected | is_new_group | streak_group | expected_unsigned | actual |
              +--------+------------+-----------+----------------+----------+--------------+--------------+-------------------+--------+
              | A | 2019-01-01 | t | | 0 | 1 | 1 | 0 | 0 |
              | A | 2019-01-03 | t | t | 1 | 0 | 1 | 1 | 1 |
              | A | 2019-01-04 | t | t | 2 | 0 | 1 | 2 | 2 |
              | A | 2019-01-09 | f | t | 0 | 1 | 2 | 0 | 0 |
              | A | 2019-01-10 | f | f | -1 | 0 | 2 | 1 | -1 |
              | A | 2019-01-11 | f | f | -2 | 0 | 2 | 2 | -2 |
              | A | 2019-01-15 | t | f | 0 | 1 | 3 | 0 | 0 |
              +--------+------------+-----------+----------------+----------+--------------+--------------+-------------------+--------+





              share|improve this answer



























                4












                4








                4







                I've done this in stages using CTEs so that you can see how it's done as the queries progress. Each CTE adds a column in the output in order to show you progress.



                It's pretty much self-documenting with the CTE names, to be honest.



                with lags as (
                select player,
                dt,
                is_winner,
                lag(is_winner) OVER (partition by player ORDER BY dt ASC) as prev_is_winner,
                expected
                from matches
                ),
                group_changes as (
                select lags.*,
                case
                when prev_is_winner <> is_winner or prev_is_winner is null
                then 1
                else 0
                end as is_new_group
                from lags
                ),
                groups_numbered as (
                select *,
                sum(is_new_group)
                over (partition by player order by dt, is_winner desc) as streak_group
                from group_changes
                ),
                expected_in_groups as (
                select groups_numbered.*,
                row_number()
                over (partition by player,streak_group
                order by dt asc, streak_group asc) - 1 as expected_unsigned
                from groups_numbered
                )
                select expected_in_groups.*, case when is_winner = 't' then expected_unsigned else expected_unsigned * -1 end as actual
                from expected_in_groups
                order by player asc, dt asc;


                DB Fiddle Link (I added an extra row just to make sure it was working at a certain point)



                Basically:




                1. lags CTE: use LAG() to get the previous result relative to the current row.


                2. group_changes CTE: Detect whether the previous streak, whether win or loss, has ended


                3. groups_numbered CTE: Give each streak a number


                4. expected_in_groups CTE: Number the rows in the group

                5. Final select: negate the loss streaks

                .



                +--------+------------+-----------+----------------+----------+--------------+--------------+-------------------+--------+
                | player | dt | is_winner | prev_is_winner | expected | is_new_group | streak_group | expected_unsigned | actual |
                +--------+------------+-----------+----------------+----------+--------------+--------------+-------------------+--------+
                | A | 2019-01-01 | t | | 0 | 1 | 1 | 0 | 0 |
                | A | 2019-01-03 | t | t | 1 | 0 | 1 | 1 | 1 |
                | A | 2019-01-04 | t | t | 2 | 0 | 1 | 2 | 2 |
                | A | 2019-01-09 | f | t | 0 | 1 | 2 | 0 | 0 |
                | A | 2019-01-10 | f | f | -1 | 0 | 2 | 1 | -1 |
                | A | 2019-01-11 | f | f | -2 | 0 | 2 | 2 | -2 |
                | A | 2019-01-15 | t | f | 0 | 1 | 3 | 0 | 0 |
                +--------+------------+-----------+----------------+----------+--------------+--------------+-------------------+--------+





                share|improve this answer















                I've done this in stages using CTEs so that you can see how it's done as the queries progress. Each CTE adds a column in the output in order to show you progress.



                It's pretty much self-documenting with the CTE names, to be honest.



                with lags as (
                select player,
                dt,
                is_winner,
                lag(is_winner) OVER (partition by player ORDER BY dt ASC) as prev_is_winner,
                expected
                from matches
                ),
                group_changes as (
                select lags.*,
                case
                when prev_is_winner <> is_winner or prev_is_winner is null
                then 1
                else 0
                end as is_new_group
                from lags
                ),
                groups_numbered as (
                select *,
                sum(is_new_group)
                over (partition by player order by dt, is_winner desc) as streak_group
                from group_changes
                ),
                expected_in_groups as (
                select groups_numbered.*,
                row_number()
                over (partition by player,streak_group
                order by dt asc, streak_group asc) - 1 as expected_unsigned
                from groups_numbered
                )
                select expected_in_groups.*, case when is_winner = 't' then expected_unsigned else expected_unsigned * -1 end as actual
                from expected_in_groups
                order by player asc, dt asc;


                DB Fiddle Link (I added an extra row just to make sure it was working at a certain point)



                Basically:




                1. lags CTE: use LAG() to get the previous result relative to the current row.


                2. group_changes CTE: Detect whether the previous streak, whether win or loss, has ended


                3. groups_numbered CTE: Give each streak a number


                4. expected_in_groups CTE: Number the rows in the group

                5. Final select: negate the loss streaks

                .



                +--------+------------+-----------+----------------+----------+--------------+--------------+-------------------+--------+
                | player | dt | is_winner | prev_is_winner | expected | is_new_group | streak_group | expected_unsigned | actual |
                +--------+------------+-----------+----------------+----------+--------------+--------------+-------------------+--------+
                | A | 2019-01-01 | t | | 0 | 1 | 1 | 0 | 0 |
                | A | 2019-01-03 | t | t | 1 | 0 | 1 | 1 | 1 |
                | A | 2019-01-04 | t | t | 2 | 0 | 1 | 2 | 2 |
                | A | 2019-01-09 | f | t | 0 | 1 | 2 | 0 | 0 |
                | A | 2019-01-10 | f | f | -1 | 0 | 2 | 1 | -1 |
                | A | 2019-01-11 | f | f | -2 | 0 | 2 | 2 | -2 |
                | A | 2019-01-15 | t | f | 0 | 1 | 3 | 0 | 0 |
                +--------+------------+-----------+----------------+----------+--------------+--------------+-------------------+--------+






                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited 8 hours ago

























                answered 8 hours ago









                PhilᵀᴹPhilᵀᴹ

                25.9k65691




                25.9k65691




















                    codigofontes is a new contributor. Be nice, and check out our Code of Conduct.









                    draft saved

                    draft discarded


















                    codigofontes is a new contributor. Be nice, and check out our Code of Conduct.












                    codigofontes is a new contributor. Be nice, and check out our Code of Conduct.











                    codigofontes is a new contributor. Be nice, and check out our Code of Conduct.














                    Thanks for contributing an answer to Database Administrators Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f235306%2fshow-current-row-win-streak%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    ValueError: Error when checking input: expected conv2d_13_input to have shape (3, 150, 150) but got array with shape (150, 150, 3)2019 Community Moderator ElectionError when checking : expected dense_1_input to have shape (None, 5) but got array with shape (200, 1)Error 'Expected 2D array, got 1D array instead:'ValueError: Error when checking input: expected lstm_41_input to have 3 dimensions, but got array with shape (40000,100)ValueError: Error when checking target: expected dense_1 to have shape (7,) but got array with shape (1,)ValueError: Error when checking target: expected dense_2 to have shape (1,) but got array with shape (0,)Keras exception: ValueError: Error when checking input: expected conv2d_1_input to have shape (150, 150, 3) but got array with shape (256, 256, 3)Steps taking too long to completewhen checking input: expected dense_1_input to have shape (13328,) but got array with shape (317,)ValueError: Error when checking target: expected dense_3 to have shape (None, 1) but got array with shape (7715, 40000)Keras exception: Error when checking input: expected dense_input to have shape (2,) but got array with shape (1,)

                    Ружовы пелікан Змест Знешні выгляд | Пашырэнне | Асаблівасці біялогіі | Літаратура | НавігацыяДагледжаная версіяправерана1 зменаДагледжаная версіяправерана1 змена/ 22697590 Сістэматыкана ВіківідахВыявына Вікісховішчы174693363011049382

                    Illegal assignment from SObject to ContactFetching String, Id from Map - Illegal Assignment Id to Field / ObjectError: Compile Error: Illegal assignment from String to BooleanError: List has no rows for assignment to SObjectError on Test Class - System.QueryException: List has no rows for assignment to SObjectRemote action problemDML requires SObject or SObject list type error“Illegal assignment from List to List”Test Class Fail: Batch Class: System.QueryException: List has no rows for assignment to SObjectMapping to a user'List has no rows for assignment to SObject' Mystery